-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crash while adding Nodes or Repos #51
Comments
Yep, got the report through Play Store. Does this apk fix it? Edit: Forget it, this doesn't work. Will upload a fixed apk later. |
I think I'm experiencing this same bug. To reproduce,
Logcat: https://github.com/firecat53/github_attachments/blob/master/syncthing_repo_add_crash.tar.gz I also tried the exact same sequence with the 2nd APK you provided above with the same results. Logcat: https://github.com/firecat53/github_attachments/blob/master/syncthing_repo_add_crash_test_apk.tar.gz Let me know if this is the same issue or if we need to open a new ticket for this. Thanks! |
@firecat53 Both of your logs say "Syncthing binary returned error code 3". Have a look at #52 (reinstall/reboot). |
Same here on Nexus 10. Though it now launches, adding repo or node causes crash. Logcat points at your own code:
|
@rkfg: Which apk/version were you using? |
The last one you posted here, https://dl.dropboxusercontent.com/u/22457329/syncthing-android-armeabi_v7a-issue-51-2.apk Market version crashes as well on adding repo/node (the reason I'm writing here), but the trace is different:
|
Okay, I did another approach and fixed it by making the repo/node settings fullscreen, instead of a dialog. This might not look as good (lots of empty space probably), but at least it works. Maybe I can revisit this in the future |
App crashes when pressing
"Add Node" or "Add Repo" or trying to open a already added Repo.
adding Nodes and Repos via the menu "Web GUI" works.
Android: 4.4.2
Samsung Note 8 - GT-N5110
Syncthing Android Version: 0.4.0 - 29.06.2014
Synthing Version: v0.8.17
The text was updated successfully, but these errors were encountered: