Thanks, tested

Also this can be followed upstream:

We can follow this upstream:

1. Each alert has "id" so when downloaded again it can be easily identified.
2. Each informed_entity is either a line or a stop. This could be translated in "a bell like" notification, that is displayed when the arrivals are shown with the stop (Or the line)
3. The description_text can be put in a nice dialog that shows when the bell icon is touched
4. We should account for the possibility of multiple alerts on a single stop, or line

sha256 2075afb945a168267e1d8b19c1bf5113a6e874d526873c1b7309de2ebce550bc ./app/build/outputs/apk/gitpull/app-gitpull-signed.apk

Let's go

Uhmm you didn't update the changelogs

Tested without nuclear implosions on a real-world device, thanks asd

sha256 11f46d95e98f8a5ccdb3a167b82480eedaf0f8d68d643ef47159a33f511054c5 ./app/build/outputs/apk/gitpull/app-gitpull-signed.apk

• Make line element clickable

Thanks, tested, no nuclear implosions, no backdoors asd

sha256 6b5848f1ae07e3a1b9f2d37b3ade8b9ac81f0edb49e6a12e08692efb7d1af509 ./app/build/outputs/apk/gitpull/app-gitpull-signed.apk

• Close line fragment if the gtfs route is incorrect

Let's consider this as resolved months ago.

Let's consider this as resolved months ago.