Sean Barbeau

This could be a similar issue to #562 - we accidentally broken stop shortcuts on at least some devices due to the refactoring Activities from the `com.joulespersecond.seattlebusbot` package to the...

~~We'd also need to include the old `com.joulespersecond.seattlebusbot.BootstrapService` to handle boot events as well.~~ (Edit - thinking more, this shouldn't be needed - this Intent is generated by the Android...

Here are the old v1.7.9 manifest entries: ``` ```

Looks like the refactor is the cause - I'm able to reproduce by installing `v1.7.9`, setting a reminder, and the installing `master` branch. Reminder only triggers after OBA app `v2.0.13`...

I'm re-opening, as I've gotten a few similar feedback messages from users recently: > App Version: 2.1.1 > Model: LGLS675 > OS Version: 5.1.1 / 22 > Google Play Services...

I got more information from the above Puget Sound user - this sounds like it could be intertwined with a data issue: > The reminders never work in the morning...

Reported by another user: > App Version: 2.1.2 > Model: XT1053 > OS Version: 5.1 / 22 > Google Play Services App: 9.4.52 (236-127739847) > Google Play Services Library: 9080000...

I haven't heard any more reports of this, so I'm going to close this issue for now. It may be related to data changes (#333). I'll re-open if I get...

Re-opening, reported by another user: >App Version: 2.1.9 Model: SM-N920P OS Version: 7.0 / 24 Google Play Services App: 11.0.55 (440-156917137) Google Play Services Library: 9452000 Region/API: Puget Sound (selected...

Closing, as this sounds like it's an instance of the "pole problem", with delays jumping near the beginning of a trip after a layover: >This route at the time I...