android.database.sqlite.SQLiteConstraintException: FOREIGN KEY constraint failed

[sedrubal]

Describe the bug
In VGN-Network there seem to be some "broken" stations. Every time you search for a route from or to such a station, you can see the error message below. I think more and more stations have this problem... Deleting the app data fixes the problem.

Error description

android.database.sqlite.SQLiteConstraintException: FOREIGN KEY constraint failed (code 787 SQLITE_CONSTRAINT_FOREIGNKEY)
android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method)
android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:832)
android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:788)

Moved from schildbach/public-transport-enabler#286

To Reproduce
Steps to reproduce the behavior:

1. Go to Search-Route-View
2. Enter a "broken" stop
3. See error

Expected behavior
A route should be calculated.

Screenshots

Versions (please complete the following information):

• Transportr Version: 2.0.6
• Device: OnePlus 5
• Android Version: 9 (LineageOS 16.0)

[ialokim]

This might be related to #207. Does this only happen with "favorite" stations (aka having the star icon)?

[sedrubal]

To be honest, I don't know. I can't reproduce it right now...

[Altonss]

I couldn't reproduce this issue either, so I'll close the issue. Feel free to reopen it if it happens again, so we can investigate the bug.

[erebion]

This issue still seems to persist.

(Funnily enough, opening this issue crashes the GitHub client I use as well, for some reason.)

[Altonss]

This issue still seems to persist.

Is it related to favorite stations?

[erebion]

Is it related to favorite stations?

Does not seem to be, no stations in the relations have been previously searched for.

It only ever happened when with specific stations, I worked around that by searching to/from nearby places instead.