You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/llm/vendor/claude.md
+59Lines changed: 59 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9272,3 +9272,62 @@ The suggestion to add `Name = "com.myadventure.app"` came from a mental model wh
9272
9272
9273
9273
42
9274
9274
42
9275
+
9276
+
9277
+
9278
+
9279
+
9280
+
9281
+
9282
+
9283
+
9284
+
9285
+
9286
+
9287
+
9288
+
9289
+
9290
+
9291
+
9292
+
9293
+
9294
+
9295
+
9296
+
9297
+
9298
+
9299
+
9300
+
9301
+
42
9302
+
42
9303
+
9304
+
I still have this error
9305
+
some errors occurred
9306
+
Downloaded package ID does not match existing app ID - com.myadventure.app [MyAdventure]
9307
+
Do I need to uninstall and reinstall this app on android?
9308
+
9309
+
Yes — you need to uninstall first, then reinstall.
9310
+
9311
+
## What's happening
9312
+
9313
+
Android identifies installed apps by their package ID (`applicationId`). The version on your phone was installed when the project's `<ApplicationId>` was `com.kusl.myadventure`. You've since changed it to `com.myadventure.app`. Android treats these as two completely different apps — and it won't let you "upgrade" one to the other because, from its perspective, you're trying to install a stranger's app on top of yours. It refuses with exactly the error you're seeing.
9314
+
9315
+
This is a security feature, not a bug. If Android allowed package ID swaps via upgrade, malware could hijack an installed app's data by impersonating it with a matching signature.
9316
+
9317
+
## What to do
9318
+
9319
+
Uninstall the old one, then install the new APK:
9320
+
9321
+
```
9322
+
adb uninstall com.kusl.myadventure
9323
+
```
9324
+
9325
+
Or, on the phone itself: Settings → Apps → MyAdventure → Uninstall. Then install the new APK normally.
9326
+
9327
+
**Heads up: this wipes the app's data.** Your SQLite save file at `/data/data/com.kusl.myadventure/...` goes with it. If you have a save you care about, use the in-app export (the base64 JSON string) to copy it out *before* uninstalling, then paste it back into the new install via import.
9328
+
9329
+
## Going forward
9330
+
9331
+
Now that you've picked `com.myadventure.app` as the package ID, lock it in and don't change it again — every change forces an uninstall/reinstall and data loss for any users who've installed it. Same applies if you later publish to F-Droid or similar; the package ID is effectively a permanent identity.
9332
+
9333
+
One other thing worth checking while you're here: the keystore. If your signed CI APK is now signed with a different key than the one originally on your phone (separate issue from the package ID, but same general "Android won't let you swap identities" theme), you'll hit a *different* error after uninstall on the *next* update. As long as `ANDROID_KEYSTORE_BASE64` in your repo secrets stays stable, you're fine — just don't regenerate the keystore.
Copy file name to clipboardExpand all lines: docs/llm/vendor/output/028.txt
+64-64Lines changed: 64 additions & 64 deletions
Original file line number
Diff line number
Diff line change
@@ -1,35 +1,35 @@
1
1
kushal@fedora:~/src/dotnet/MyAdventure$ cd /home/kushal/src/dotnet/MyAdventure; time dotnet clean; time dotnet restore; time dotnet build; time dotnet test; time dotnet list package; time dotnet list package --outdated; time dotnet format; time sh export.sh;
0 commit comments