gaunty

@HuiSF any further updates regarding this? we will moving towards multi device(s)

An interesting observation , we have added logic to stop the background location, set the updated config to background location, and then start the background location when authentication state gets...

@christocracy quick question just asking if you had a chance to look at bg.BackgroundGeolocation.setConfig not being updated??

@christocracy there currently are. bg.BackgroundGeolocation.onGeofence((bg.GeofenceEvent event) async { log('[geofence] ${event.identifier}, ${event.action}'); }); bg.BackgroundGeolocation.onGeofencesChange((bg.GeofencesChangeEvent event) async { log('[GeofencesChangeEvent off] ${event.off}'); log('[GeofencesChangeEvent on] ${event.on}'); }); //this config is **only** used for the...

@fjnoyp this could do with being fixed soon.. sometimes, the completer within the amplify configure does not return in time before the next check configured is set to true, and...

@Equartey has there been any updates with this out of interest?

Also, what makes this worse is we have a schema where a parent model has a one to many relationship with children. when this happens, it is possible the children...

hi @khatruong2009 yes, along those lines.. I would do quite a few mutations also whilst being offline.. then when connection restored and the app tries to sync the mutations ,the...

hi @khatruong2009 this is our live cognito setup Refresh token expiration 365 day(s) Access token expiration 1 day(s) ID token expiration 1 day(s) For our staging to make this more...

hi @khatruong2009 I find it easiest to reproduce using a real IOS device and use the Network Link conditioner, and setting this to 100% loss I have this also have...