Bruno Viana de Siqueira

Results 37 comments of Bruno Viana de Siqueira

Looking at an iOS user specific behavior: 1- User is logging in normally and using our app (I can see by his logs) 2- Following method is called and returns...

In android, the behavior changes depending on the user. One thing never changes: user gets SessionExpiredException right after signIn (on iOS seems that he gets SignedOutException). We have some users...

Digging deep into the problem, I found out a pattern. The users' devices who gets this problem right after signIn are not being listed in "Device tracking log" even though...

Look at a normal user behavior (my user): ![158654689-2faf1e94-5bbf-4ab0-8fbd-d95b7bb609f4](https://user-images.githubusercontent.com/18200284/158668778-a106c0fc-8fc2-43de-bbcf-5fee3c90f55f.png) If you see, every time I make a successful signIn after reinstalling the app, he register my device in the "Device...

You just need to send "click_action" inside "data" map.

Same here. Numerous crashes in the last 24 hours.

Here is the crash stacktrace (97 android users affecteds): ` InAppUpdatePlugin.kt line 150 Caused by android.content.IntentSender$SendIntentException android.app.Activity.startIntentSenderForResultInner (Activity.java:5519) android.app.Activity.startIntentSenderForResult (Activity.java:5487) androidx.activity.ComponentActivity.startIntentSenderForResult (ComponentActivity.java:631) com.google.android.play.core.appupdate.zze.startIntentSenderForResult (com.google.android.play:core@@1.10.3:1) com.google.android.play.core.appupdate.zzf.startUpdateFlowForResult (com.google.android.play:core@@1.10.3:9) com.google.android.play.core.appupdate.zzf.startUpdateFlowForResult (com.google.android.play:core@@1.10.3:2) de.ffuf.in_app_update.InAppUpdatePlugin.onActivityResumed$lambda-0 (InAppUpdatePlugin.kt:150)...

Getting StackOverflowError after upgrading to Flutter 3.7 only on iOS. We also use MultiProvider with many global providers. @rrousselGit what is your advice to solve it? Scoping providers? Stop using...

@rrousselGit So, since providers nests each other, the only solution that escalates is not to have dozens of providers above the same widget tree. Am I right?

> You can stop using MultiProvider yes. That should raise the limit quite a bit, at the cost of readability. I don't see why it would raise the limit. Wouldn't...