You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ArcherEmiya05 can you provide some logs from logcat that show the crash? There should be some evidence in there.
Thats all the what it says in logcat on 3 devices that I've tested.
E/AndroidRuntime: FATAL EXCEPTION: main
Process: package.name, PID: XXXX
Also I tried it on different device LG K10 K430dsy and Cherry Mobile J5s. All crash when device is not connected to a network. So my work around as of now is to check whether the app is connected to any network before calling fetch() or fetchAndActivate()
Activity
[-]E/AndroidRuntime: FATAL EXCEPTION: main[/-][+](Remote Config) E/AndroidRuntime: FATAL EXCEPTION: main[/+]ArcherEmiya05 commentedon Jul 2, 2019
The app close immediately without giving any details in stacktrace
samtstern commentedon Jul 3, 2019
@ArcherEmiya05 can you provide some logs from
logcat
that show the crash? There should be some evidence in there.adrianolc commentedon Jul 5, 2019
Same thing for me and there's no stacktrace :(
ArcherEmiya05 commentedon Jul 6, 2019
Thats all the what it says in logcat on 3 devices that I've tested.
E/AndroidRuntime: FATAL EXCEPTION: main
Process: package.name, PID: XXXX
Also I tried it on different device LG K10 K430dsy and Cherry Mobile J5s. All crash when device is not connected to a network. So my work around as of now is to check whether the app is connected to any network before calling
fetch()
orfetchAndActivate()
ben-mathu commentedon Jan 19, 2021
Any updates on this issue? Did you find a solution?
rugovit commentedon Jun 15, 2021
happens on my app as well, no stacktrace