Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up(Remote Config) E/AndroidRuntime: FATAL EXCEPTION: main #902
Comments
ArcherEmiya05
changed the title
|
The app close immediately without giving any details in stacktrace |
|
@ArcherEmiya05 can you provide some logs from |
|
Same thing for me and there's no stacktrace :( |
Thats all the what it says in logcat on 3 devices that I've tested. E/AndroidRuntime: FATAL EXCEPTION: main 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 |
Step 1: Describe your environment
Step 2: Describe the problem:
Steps to reproduce:
(Offline only) App crash whenever the device is not connected to internet.
Observed Results:
E/AndroidRuntime: FATAL EXCEPTION: main
Relevant Code:
Calling
fetch()orfetchAndActivate()insideonResume()