stefan-niedermann
Cards never getting created
This issue respects the following points:
- [x] I have read the FAQ
- [x] I have searched for existing issues
- [x] The issue affects the Deck Android app, neither the Deck server app nor the Nextcloud Android app.
Describe the bug
General: I am logged in to my nextcloud account. Deck APK 1.24.5 (same with 1.24.1) is installed. Deck cards are correctly loaded and visible within the deck apk.
Problem description: When I try to create a deck using the APK it gets stuck in the add card context forever withou(I cancelled after 15 minutes)
Steps:
- Install app
- Select user
- Import decks
- Open any deck
- Click on "+" (add card)
- Insert some name
- Press edit OR save
Additional: When I try to create a board using APK I get a synchronization failed error and a log output. I already saw a similar issue (https://github.com/stefan-niedermann/nextcloud-deck/issues/1307) to this but maybe it is also related to my "create card issue". Find log attached.
Expected behavior
Card creation The cards is created or I get an error description, timeout error, or some information why the card is not able to be created.
Deck creation Deck gets created and is accessable
Deck Android version
1.24.5
Deck server version
1.14.3
Nextcloud Android version
3.30.8
Nextcloud version
30.0.5
Device
Xiaomi 13
Android Version
15
App Store
- [ ] Google Play Store
- [ ] Google Play Store (Beta channel)
- [x] F-Droid
- [ ] Huawei App Gallery
Stacktrace
App Version: 1.24.5
App Version Code: 1024005
Server App Version: 1.14.3
App Flavor: fdroid
Files App Version Code: 30300890 (com.nextcloud.android.sso.model.FilesAppType@65897f3)
---
OS Version: 5.15.148-android13-8-00004-ge488687c12ef-ab11838684(OS2.0.2.0.VMCEUXM)
OS API Level: 35
Device: fuxi
Manufacturer: Xiaomi
Model (and Product): 2211133G (fuxi_eea)
---
java.lang.IllegalStateException: Owner is null. This can be the case if the Deck app has never before been opened in the webinterface
at it.niedermann.nextcloud.deck.repository.SyncRepository.lambda$createBoard$7(SyncRepository.java:351)
at it.niedermann.nextcloud.deck.repository.SyncRepository.$r8$lambda$Jsqb4qpFhMo5awS5L6i_NN3tSnM(Unknown Source:0)
at it.niedermann.nextcloud.deck.repository.SyncRepository$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at it.niedermann.nextcloud.deck.util.ExecutorServiceProvider$RetryableRunnable.run(ExecutorServiceProvider.java:66)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Hi @suly520, thanks for your report!
I'd suggest analyzing this top-down: I think the Owner is null part is the topmost problem here, so lets have a look:
Can you please try it with the following DEV version: ʕっ•ᴥ•ʔっ zipped APK download How to use the DEV version
I enhanced the logs so it shows what user should be the expected owner and what users are known to the database. (if you post it here: redact names if needed)
App Version: 1.24.5 App Version Code: 1024005 Server App Version: 1.14.3 App Flavor: dev
Files App Version Code: 30300890 (com.nextcloud.android.sso.model.FilesAppType@ac9dee1)
OS Version: 5.15.148-android13-8-00004-ge488687c12ef-ab11838684(OS2.0.2.0.VMCEUXM) OS API Level: 35 Device: fuxi Manufacturer: Xiaomi Model (and Product): 2211133G (fuxi_eea)
java.lang.IllegalStateException: Owner is null. This can be the case if the Deck app has never before been opened in the webinterface. More:
account_id:[REDACTED_ACCOUNT_1]
username:[REDACTED_USER_1]
List of available Users:[REDACTED_USER_1]
uid:[REDACTED_USER_2] | account_id:[REDACTED_ACCOUNT_1]
uid:[REDACTED_USER_3] | account_id:[REDACTED_ACCOUNT_1]
uid:[REDACTED_USER_4] | account_id:[REDACTED_ACCOUNT_1]
uid:[REDACTED_USER_5] | account_id:[REDACTED_ACCOUNT_1]
uid:[REDACTED_USER_6] | account_id:[REDACTED_ACCOUNT_1]
uid:[REDACTED_USER_7] | account_id:[REDACTED_ACCOUNT_2]
uid:[REDACTED_USER_3] | account_id:[REDACTED_ACCOUNT_2]
uid:[REDACTED_USER_4] | account_id:[REDACTED_ACCOUNT_2]
uid:[REDACTED_USER_2] | account_id:[REDACTED_ACCOUNT_2]
uid:[REDACTED_USER_5] | account_id:[REDACTED_ACCOUNT_2]
uid:[REDACTED_USER_6] | account_id:[REDACTED_ACCOUNT_2]
at it.niedermann.nextcloud.deck.repository.SyncRepository.lambda$createBoard$7(SyncRepository.java:352)
at it.niedermann.nextcloud.deck.repository.SyncRepository.$r8$lambda$Jsqb4qpFhMo5awS5L6i_NN3tSnM(Unknown Source:0)
at it.niedermann.nextcloud.deck.repository.SyncRepository$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at it.niedermann.nextcloud.deck.util.ExecutorServiceProvider$RetryableRunnable.run(ExecutorServiceProvider.java:66)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Hello @desperateCoder, thanks for investigation in my issue! I also created a new user on my nextcloud instance to check if I get an error there. With the new created account I don't get errors.
@suly520 Thanks for testing, glad we made some progress!
Just to make sure: Is this resolved for you then? I'm not sure if your initial problem is still a problem or not 😅
If you're fine for now, feel free to close this issue :)
I just moved to a different user as a workaround so the bug still exists or is obsolete due to the version in which the user where created So I think this issue can be closed.