• I was using the cutting Edge build: espruino_2v13.123_banglejs2 in the last days until I found out that no notifications at all are shown on the watch via Android Gadgetbridge.

    Today I switched back to 2v13 release and notifications are working again.

    I had no time yet to find out which build does the regression.

  • Nice to see I'm not the only one experiencing this...
    https://github.com/espruino/Espruino/iss­ues/2207

  • Ya, I have the same. I was about to sell the watch as the unreliable notifications make it not useful in my life :(
    I hope we can get the notifications to be more reliable so I can count on them. With the 'memory_busy' and FIFO errors, it's quite frustrating.

  • I also want to say that I do see improvements on an almost daily basis and that the platform is seriously good.

  • I had the same experience.
    I flashed back to the stable version and then upgraded again to 2v13.123 and on the second try the notifications work again.

  • Interesting. I tried flashing back 2v13.123 a couple of times and notifications never worked.

  • I think I have identified the problem and found a workaround:
    https://github.com/espruino/Espruino/iss­ues/2215

    With the described workaround in the weather lib it seems to work fine for me. Removing the weather app would probably work the same way.

  • I think I saw the same behaviour (no notifications on 2v13.123) with only the default apps installed as well, but can't quite remember at the moment.

  • I have deinstalled some of the default apps, there might be a similar workaround necessary in one of those. My current set of apps works fine with the weather lib workaround, while I do no get any notifications from Gadgetbridge without it.

  • I tried just now with uninstalling the Weather app on 2v13.123, but it made no difference. Installing the app again wasn't possible until I flashed back stable 2v13 though, so there's definitely something going on with the weather lib.

  • I have set up 2v13.123 with install of default apps in stable app loader. Then installed Android and Messages. Notifications are working fine.

    After installing Weather the console shows the following error, no Notification on the Bangle:

    >GB({"t":"notify","id":1575479849,"src":­"Hangouts","title":"A Name","body":"message contents"})
    Uncaught ReferenceError: "_GB" is not defined
     at line 7 col 59 in weather
    ...eather")update(event);if(_GB)setTimeo­ut(_GB,0,event);
                                   ^
    in function "GB" called from line 1 col 94
    ...,"body":"message contents"})
    

    After removing Weather app notifications work again.

  • I have set up 2v13.123 with install of default apps in stable app loader. Then installed Android and Messages. Notifications are working fine.

    Yes, I was receiving notifications this weekend on 2v13.123 and it was fine, so I guess it's the addition of the weather app that is causing issues now?

    Rather than talking about this in 3 places, maybe we can keep technical discussions to https://github.com/espruino/Espruino/iss­ues/2207 and https://github.com/espruino/Espruino/iss­ues/2215

    But unfortunately if I provide cutting edge builds, then in them things may end up broken - especially after a big change like this to add proper support for let+const

  • Yes, breakage is to be expected in cutting edge builds. I think most people understand that and are happy to help squashing some bugs by testing.
    I have posted a example in the Github discussion, it seems to be a somewhat strange problem only surfacing in specific combinations of let/const/var/require/exports.

  • Thanks! Hopefully that issue is now fixed!

    There may well be some other gotchas though even if Espruino is working perfectly. There's one change recently where an app wasn't using let correctly and the Linter didn't pick it up, so there may be some others I'd afraid

  • Works fine with my minimal setup on 2v13.138, seems to also work proper with my daily driver bangle with lots of apps installed. At least it throws no errors in the IDE as it did before ;)

  • Confirmed working as expected on 2v13.138.

  • Yes, breakage is to be expected in cutting edge builds. I think most people understand that and are happy to help squashing some bugs by testing.

    Yes, absolutely!
    [Maybe http://forum.espruino.com/conversations/­376706/ was also somehow related? Didn't work in 13.123 but fine again in 13.138]

  • That might well be, since an error during the boot code could prevent the other stuff from execution. For me it stopped the quiet mode and alarms from triggering, since those load later while booting and were not executed after the errors caused by the weather widget.

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

No notifications on 2v13.123 cutting edge build

Posted by Avatar for myxor @myxor

Actions