[iOS Integration] Notification forwarding unreliable #4175
Description
Affected hardware version
Bangle 2
Your firmware version
2v28.102
The bug
Since a while ago, notification forwarding has become increasingly unreliable, with both me and @eisengpferd having issues with iOS pairing. For me at least, it looked like the pairing was unstable when switched to an iflash build. However, after more looking into it, it seems as though an error occurs when a notification is received, and is not displayed because of that. Currently it looks like it's a problem with the auto-detection of app names, where its trying to get the object name of something that doesn't exist. However, it works some of the times, and other times it stops. Data notifications such as BangleDumpWeather are still received and parsed by the watch. I'll look into it more, and hopefully come up with a PR shortly.
Installed apps
taglaunch (0.09), messageicons (0.17), reply (0.03), messagegui (0.92), setting (0.82), sched (0.36), alarm (0.52), notify (0.14), health (0.37), sleeplog (0.24), clockbg (0.08), clock_info (0.27), ultrainfo (0.01), widlock (0.08), widmessages (0.07), messages (0.70), mylocation (0.11), ios (0.24), smpltmr (0.13), weather (0.31), boot (0.69), widbtstates (0.03), wid_a_battery_widget (0.05), locale (0.20), clkinfomsg (0.01), clkinfosunrise (0.05), myprofile (0.02), clkinfodist (0.01), loadingscreen (0.01), themes (0.01), calculator (0.08), worldclkinfo (0.02)