Closed AeliusSaionji closed 10 months ago
Thanks for your interest in Atmos Weather! I will look into this issue shortly.
Based on the error and Android version you are using, it looks like the crash was caused by this change in Android 14. In the past, I had taken for granted that the SCHEDULE_EXACT_ALARM
permission was given by default and that users would not manually revoke the permission. The app uses the SCHEDULE_EXACT_ALARM
permission to check for weather alerts regularly. For now, you should be able to use Atmos by manually granting permission to set alarms in app info. In the near future, I plan to release an update that adds additional permission checks and requests the permission properly.
I have reviewed the alarm code and believe I have fixed all Android 14 alarm issues. I will be confirming the fixes with an emulator soon. It is admittedly not a very graceful solution - for now, it just opens the settings page for alarms without a proper explanation for why the permission is needed. However, the app will no longer crash on Android 14. If the permission is not granted, Atmos Weather will continue to work with degraded notification performance. In a future update, I plan to overhaul the permissions request flow on Android to explain permissions to the user.
Tested - fix works. While testing, I also discovered that notifications are disabled by default in Android 14 as well. I have added another fix to request the notification permission for Android 14. As with the last fix, this is not a graceful solution, but it will have to do until I have more time to completely revamp the permissions setup.
Both issues are confirmed fully fixed now. I will be releasing Atmos Weather v2.0.2 shortly with the fixed code.
Atmos Weather v2.0.2 has been released! (https://github.com/atticuscornett/AtmosWeather/releases/tag/v2.0.2)
Version Info