Skip to content
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 crashes when checking tasks #34

Closed
Foggalong opened this issue Mar 15, 2016 · 9 comments
Closed

App crashes when checking tasks #34

Foggalong opened this issue Mar 15, 2016 · 9 comments
Labels
bug Something is not behaving as the developers expected confirmed The developers have been able to confirm that the issue is valid
Milestone

Comments

@Foggalong
Copy link

The app crashes for me when trying to check a task as done. There's no option to send an error report so I'm not sure what else I can add, but I'm running on CM13 on the nexus 10.

@iSoron
Copy link
Owner

iSoron commented Mar 15, 2016

Thank you for reporting it here. The option to send the report automatically only shows up if you install the app through Google Play Store. If you have installed it through F-Droid or something else, here is how you can get useful information to help us track the bug. In short, you need to install an app like CatLog, set the filter to "org.isoron.uhabits", and then save or email yourself the log. It is a bit of trouble, but it would help a lot.

If you just want to get rid of the bug, you could try to change the frequency of the habit to something else, and then change it back to the original. For example, change it to 1 repetition in 7 days, and then change it back.

@iSoron iSoron added bug Something is not behaving as the developers expected needs-info The developers need more information to tackle this issue labels Mar 15, 2016
@Foggalong
Copy link
Author

Is this what you need?
tmp_13663-screenshot_20160315-1359591188363046

@Foggalong
Copy link
Author

As a note, changing the frequency doesn't seem to surpress the bug either.

@iSoron
Copy link
Owner

iSoron commented Mar 15, 2016

Thank you, this is exactly the information that I needed. I will try to reproduce this bug on my phone soon. As a workaround, I guess you can you still toggle the checkmarks using widgets, reminders, or using the history editor.

Just a few questions to make this bug easier to reproduce. 1) Does this happen with every habit and every checkmark, or only with a particular combination? 2) Has this happened since the first time you installed the app, or was it after you updated the app / deleted some habit / something else?

@Foggalong
Copy link
Author

  1. Happens with every habit and every check mark
  2. I only installed the app today, and after a bit of testing happens with both v1.2 and v1.3
  3. Marking a task as done via widget doesn't register it as done within the app

@iSoron
Copy link
Owner

iSoron commented Mar 15, 2016

Okay, I think I might have been able to reproduce the bug on my tablet. Just to confirm that this is indeed the same bug, could you please try to run the app when your tablet is in portrait mode, instead of landscape?

@iSoron iSoron added this to the Loop 1.3.1 milestone Mar 15, 2016
@Foggalong
Copy link
Author

Can confirm it works in portrait mode, and as an added bonus the stuff toggled via widget also shows up in portrait mode.

@iSoron iSoron added confirmed The developers have been able to confirm that the issue is valid and removed needs-info The developers need more information to tackle this issue labels Mar 15, 2016
@iSoron iSoron closed this as completed in 8102c18 Mar 16, 2016
@iSoron
Copy link
Owner

iSoron commented Mar 16, 2016

I have released version 1.3.1 just now, which contains a patch to fix this bug. It might take a couple of days for it to show up on F-Droid, and a couple of hours for it to show up on Google Play Store. Thank you for the detailed report.

@Foggalong
Copy link
Author

No problem, thanks for the fix! :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not behaving as the developers expected confirmed The developers have been able to confirm that the issue is valid
Projects
None yet
Development

No branches or pull requests

2 participants