Semesterticket does not update

[JeroTek]

Hello there,

started the App on April 1. and again on the following days, but no new Semesterticket for the Summertime.

Tried to redo my credentials, got stuck with the same error message as in #191 so tried to reinstall the app as stated in the solution from back then.

Did not work, error message when trying to send my credentials "Fehler beim Laden des Tickets!"

Tried again but cleared cache before clearing storage, same error.

OS: e/os/ on FP5
Store: Aurora Store
App Build number v2.3.4 (57)

same user behind this github acc. and the other acccount back in #191 and #179

will use a screenshot for now, hopefully not a widespread error..

[domai-tb]

Hey, unfortunately I could not find the cause of the error and could not reproduce it reliably. We are working on it.

[JLamperti]

Having experienced this issue myself, here are a few pointers:
when i couldnt update the ticket, attempting to re-request it displayed a generic "something went wrong connecting to the server" message.
To resolve it, i did the following steps:

• go through the ride ticketing app again and access my ticket for the current semester
• log in in the RUB-App again
  IIRC it didnt work immediately, but the next day the ticket was there.

This leads me to assume that the RUB-App might be successfully requesting an existing Ticket, but to generate it one must use the convoluted Process with the ride ticketing app once per semester - or possibly implement the whole flow inside the RUB app
Maybe be would be easier to display a warning that the ticket couldnt be updated, and suggest accessing it through the ride ticketing app once.

[domai-tb]

Hey @JLamperti, thanks for investigating the issue. 👍🏼

The current ticket loading process is implemented within a HeadlessInAppWebView that calls the Ride Ticketing webpage. But sadly, the injected JavaScript of lib/pages/wallet/ticket/ticket_datasource.dart doesn't work reliable - it just doesn't work sometimes. We couldn't identify the root cause, but we never thought about the re-generation process of the ticket on Ride's side.

I would really, really appreciate if someone could investigate the JavaScript handlers. At our AStA teams side we have a really high workload while finishing the Raumfinder - PR #188. 🙏🏼