Hello,
i am using the app db navigator on a daily basis. For the last month or so the app became more and more unstable. To book a ticket, I had to go back and forth several times. But it worked. Since the update to 4.5 the app does not work anymore. The booking process just stops somewhere. What I did already try: Remove the app and reinstall a previous version. It got worse. I even can’t login to my account. Could there be any problem with the app triggering the browser to open? Because a login in the db app in principle requires a login via browser, but the browser is not opened.
Since there are some users from Germany, could you share your experiences or do have a working set up?
I don’t buy tickets with DB navigator, because I don’t do payments on the phone for security reasons. But I am using DB navigator regularly for anything else and it works just fine on my 10 III. I had trouble to login via the SFOS browser in the past. At some point I installed Vivaldi and made it the default browser which solved any login problems (also for other apps).
Not sure how this can help you just so you know that DB navigator is usable with SFOS.
I see. The only thing I can think of is to check the “Open by default” group in the app’s Android settings and make sure that it has permission to open supported links and bahn.de is among them.
If this looks alright, someone else, who is more knowledgeable than me, might be able to point out which log files one should check.
AFAIR I haven’t bought new tickets wit DB-Navigator on 4.5., yet. (XA2+) Also, I didn’t have to login on 4.5. However, loading tickets, comfort check-in, ‘real-time’ timetable, etc worked without issues.
Yes, I also installed the FireFox browser. The forwarding of DB-Navigator works with FireFox. With the SFOS browser I only get a white display and the transaction breaks off.
Apparently you need an Android browser installed to handle the log-in request from the navigator app within the AndroidApp Support Container. The release notes for 4.5 mentioned changes in the AAS security architecture, that might be the reason for the change.
To clarify this more explicitly, your problem is that the DB navigator App opens the Browser for login. The aliendalvik default is the preinstalled, SailfishOS-native browser. Which, at least for me, never worked for this.
To fix this, install Fennec from F-Droid, then goto the Android settings of Fennec and set it as default browser inside of Aliendalvik. Afterwards, you’ll use Fennec for login and it’ll work fine.
Thank you all for your support. I really got it to work. First I was disappointed about the responses. Because my problem was definitely a different one than the old ‘browser is not handled correctly’ issue. And I did already have an android browser (opera). But after installing firefox, i was able to select one of the browsers to enter my login data.
