[Bug]: Unable to delete notification since 1c0ddefad9
#20
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi
Thanks for your great work as always :)
The build : https://gitea.angry.im/PeterCxy/OpenEUICC/actions/runs/4
Commit :
9f3977dc5e
Do work for manipulating notifications (deleting notification)
But since the following builds notifications can not be deleted any more, after the delete action nothing happen and the notification remain present, nothing is visible in the app logs on delete action.
The next build : https://gitea.angry.im/PeterCxy/OpenEUICC/actions/runs/5
Commit :
1c0ddefad9
Introduced the bug and its not working since that build (5) included.
System :
Thanks
1c0ddefad9
istNotification
functionOr
1c7dc67803
lpac_notifications_init()
functionIs responsible, I red the commit code but did not notice the exact issue, I don't have the environment to test/debug...
Thanks
Thanks a lot for your pr :)
I think the issue is half fixed... tried for some random notifications deletion after the update and it worked, and today it did not work after a profile deletion, I had to downgrade to the working version to be able to delete the notification... here are the logs, I think the failure at the beginning are from the last version while the success operation are after the downgrade...
the crash may not be related to the issue...
server of the notif : https://trl.prod.ondemandconnectivity.com/gsma/rsp2/es9plus/handleNotification
@moon-cacke Honestly I don't think this is a problem that can be fixed from OpenEUICC side. If
getProfiles()
raises a null pointer exception, it means that either your modem has not refreshed properly after a eUICC profile switch (this could happen when you delete a profile), or the eUICC itself is stuck in a werid state. This is unrelated to OpenEUICC's version and there has been no change on this part.All I can do here is maybe to stop OpenEUICC from crashing if it gets in that weird state, but there is nothing that can be done from OpenEUICC or LPAC to fix the situation. The device itself must be reset to get out of that state.