App Crash on Launch: Room Database Migration Error (from 18 to 13)

[nathanmota-dev]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Android

Body

Describe the bug

The GitHub Android app crashes immediately upon opening due to a database migration failure (Room RoomDatabase.Builder).

Steps to reproduce

1. Open the GitHub app.
2. The app crashes immediately and closes.

Stack Trace / Logs

java.lang.IllegalStateException: A migration from 18 to 13 was required but not found. Please provide the necessary Migration path via RoomDatabase.Builder.addMigration(Migration ...) or allow for destructive migrations via one of the RoomDatabase.Builder.fallbackToDestructiveMigration* methods.
	at j4.k0.g(Unknown Source:410)
	at j4.k0.e(Unknown Source:0)
	at androidx.sqlite.db.framework.d.onDowngrade(Unknown Source:14)
	at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:435)
	at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:336)
	at androidx.sqlite.db.framework.d.k(Unknown Source:4)
	at androidx.sqlite.db.framework.d.t(Unknown Source:47)
	at androidx.sqlite.db.framework.d.b(Unknown Source:21)
	at androidx.sqlite.db.framework.e.B0(Unknown Source:9)
	at j4.g0.c(Unknown Source:10)
	at vh.a.c(Unknown Source:453)
	at vh.a.call(Unknown Source:89)
	at j4.h.m(Unknown Source:7)
	at b60.a.h(Unknown Source:8)
	at s60.g0.run(Unknown Source:115)
	at g.m0.run(Unknown Source:643)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
	at java.lang.Thread.run(Thread.java:1563)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [r1{Cancelling}@4c9922b, Dispatchers.Main.immediate]

Environment

• Device: Xiaomi Poco F7
• OS Version: Android 16
• GitHub App Version: Last for Play Store

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[nathanmota-dev]

I went to "Clear Data" and deleted the data, and the app worked. However, it took me days to figure out the error because the log trace was from my phone, not the app.

[nathanmota-dev]

Clear Data for your phone