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 wont start #123

Closed
brokenbadger opened this issue Oct 24, 2024 · 14 comments · Fixed by #124 or #125
Closed

App wont start #123

brokenbadger opened this issue Oct 24, 2024 · 14 comments · Fixed by #124 or #125
Labels
bug Something isn't working

Comments

@brokenbadger
Copy link

Since last update, app crashes on boot screen (logo).
Cannot use.

@AdamGuidarini
Copy link
Owner

Hello, sorry to hear that. Could you provide a few more details?

  • What version of Android are you using?
  • What do the schedules for your medications look like? Daily, multiple per day, other intervals?
  • Do you medications have any non-alphanumeric characters in their, names, dosage units, aliases, or instructions? I don't think this would cause it, but I usually don't use non-alphanumeric characters in my tests so it's something I may have missed

@K4LCIFER
Copy link

I have the same issue. It's instantly crashing when I open the app. This only started occurring after using the most recent update v0.13.0. I'm on Android 15. App is installed via F-Droid.

@AdamGuidarini AdamGuidarini added the bug Something isn't working label Oct 25, 2024
@AdamGuidarini
Copy link
Owner

AdamGuidarini commented Oct 25, 2024

Doing some tests with Android 15 in an emulator. I haven't been able to reproduce this yet. I installed version 0.12.9 first, created 1 medication with each type of schedule, letting the notifications trigger, checking a couple then updating to 0.13.0 and letting the notifications trigger again but haven't managed to encounter the issue yet.

Are there any details you'd be comfortable sharing about the medications (schedule, dosage unit, etc..) that might help me recreate the issue in case it's related to the specific data?

It might also be worth trying to clear the app's cache. I'm not sure if it's in fact a data issue, but it might be worth trying

https://www.androidpolice.com/clear-app-cache-data-android/

@brokenbadger
Copy link
Author

Hi,

  • I'm using android version 14
  • My schedules are one medication at 08:00 and the other at 20:00 with reminders for both.
  • Medications only use standard characters for both names and dosages.
  • I've not changed anything since the previous version which worked perfectly. It worked perfectly before the update and now it just won't boot?
  • I do use Nova launcher if thats of any consequence, but like I say, it ran flawlessly before?

Thanks for looking into this, app has been a must have for me.

@K4LCIFER
Copy link

K4LCIFER commented Oct 25, 2024

It might also be worth trying to clear the app's cache. I'm not sure if it's in fact a data issue, but it might be worth trying

I cleared the cache, but the app still immediately crashes on open.


Are there any details you'd be comfortable sharing about the medications (schedule, dosage unit, etc..) that might help me recreate the issue in case it's related to the specific data?

Not much comes to mind. The only thing that I do often that is possibly different than the usual flow is that I manually change dates/times in historic data, and I add custom units of "ug" to a medication on historic entries.


One perhaps helpful note is that notifications from the app are still coming through for medication reminders.

@K4LCIFER
Copy link

K4LCIFER commented Oct 25, 2024

I do use Nova launcher if thats of any consequence, but like I say, it ran flawlessly before?

I'm using the stock android launcher.


Medications only use standard characters for both names and dosages.

Same for me, iirc.

@fleurc
Copy link

fleurc commented Oct 25, 2024

Hi, I'm having the same issue, I'm running Android 14. My phone model is a Motorola Moto G54. The app was fine a few days ago, now with the recent update it just doesn't run.

@brokenbadger
Copy link
Author

Just upgraded to Android 15 and cleared cache, still same issue.
All other apps are also updated.

@AdamGuidarini
Copy link
Owner

Hmm...Did you happen to have exported then imported data? I imported data from my own device into an instance of the app running in the emulator and it starts crashing immediately when I do that

@AdamGuidarini
Copy link
Owner

The importer seems to be removing the last 0 from any date it gets (formatted like this: 2024-10-25 04:30:00). I've seen this in other parts of the app and there's a little band-aid fix for it (just adding a zero back). It's not ideal but it leaking out like this means a real fix needs higher priority

@AdamGuidarini
Copy link
Owner

This release should fix this issue (assuming the bug in importing data was the cause). I'll close this issue, but if those doesn't fix the crashing feel free to reopen it or create a new one.

https://github.com/AdamGuidarini/MediTrak/releases/tag/v0.13.1

This was linked to pull requests Oct 25, 2024
@brokenbadger
Copy link
Author

Hmm...Did you happen to have exported then imported data? I imported data from my own device into an instance of the app running in the emulator and it starts crashing immediately when I do that

No, not for me?

@K4LCIFER
Copy link

K4LCIFER commented Oct 26, 2024

Hmm...Did you happen to have exported then imported data?

I didn't do that. I've exported, but I haven't imported.

I would test the app right now, but the 0.13.1 still hasn't appeared on Droid-ify for me.

@AdamGuidarini
Copy link
Owner

Migrating this conversation of to a new issue as the fix doesn't seem to have worked:

#126

I left some instructions there for how to pull the app's logs. If anyone is able to retrieve them it would go a long way to helping me patch the bug as recreating this issue is still proving difficult

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants