Nextcloud-deck: I met the next error

[neerro]

App Version: 1.15.4
App Version Code: 1015004
Server App Version: 1.2.5
App Flavor: play

Files App Version Code: 30150190

---

OS Version: 4.14.116(10.0.0.221C10)
OS API Level: 29
Device: HWHRY-H
Manufacturer: HUAWEI
Model (and Product): HRY-LX1 (HRY-LX1RU)

---

java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Long it.niedermann.nextcloud.deck.model.Card.getStackId()' on a null object reference
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.providers.CardDataProvider.goDeeperForUpSync(CardDataProvider.java:290)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.providers.StackDataProvider.goDeeperForUpSync(StackDataProvider.java:129)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.providers.BoardDataProvider.goDeeperForUpSync(BoardDataProvider.java:179)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.SyncHelper.doUpSyncFor(SyncHelper.java:122)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.SyncHelper.doUpSyncFor(SyncHelper.java:101)
    at it.niedermann.nextcloud.deck.persistence.sync.SyncManager$2$1.lambda$onResponse$0$SyncManager$2$1(SyncManager.java:243)
    at it.niedermann.nextcloud.deck.persistence.sync.-$$Lambda$SyncManager$2$1$B5Glge0jtjic-sLIZD8UEHJ-hfQ.run(Unknown Source:6)
    at java.lang.Thread.run(Thread.java:929)

[desperateCoder]

Hi @neerro, I'm a little confused, did you close this issue on purpose?

[stefan-niedermann]

1. Deck Android 1.15.4 had a known bug in combination with server Deck versions below 1.3.0. This has already been fixed meanwhile. Deck Android 1.15.5 is already published and delayed by Google ("because of Corona"...) - it should arrive soon at the Play Store in the next few days. Possible workarounds if you can't wait: Install older Deck Android versions or upgrade to NC 21 with Deck 1.3.1
2. Please stop ignoring the issue template. It is there for a reason and we will close future issue which do not fill the template without any comment.
3. I closed and locked the other issue as this is related to the Android client. Opening it multiple time will change nothing.

[neerro]

Hi @desperateCoder, I've just forwarded this issue to mobile app, as I have the problem with it. If it will be correct I re-invoke the issue here.

[neerro]

Thanks god and @stefan-niedermann of course ;) The issue has gone. Thanks ones again! I've just installed the new app version and all works well.

[neerro]

Hi! I met the same issue again after the server version of nextcloud was updated from 20 to 21.
Installed app version on mobile device is 1.15.9, server version of Deck is 1.3.1.
Help please!

App Version: 1.15.9
App Version Code: 1015009
Server App Version: 1.3.1
App Flavor: play

Files App Version Code: 30150190

---

OS Version: 4.14.116(10.0.0.221C10)
OS API Level: 29
Device: HWHRY-H
Manufacturer: HUAWEI
Model (and Product): HRY-LX1 (HRY-LX1RU)

---

java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Long it.niedermann.nextcloud.deck.model.Card.getStackId()' on a null object reference
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.providers.CardDataProvider.goDeeperForUpSync(CardDataProvider.java:290)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.providers.StackDataProvider.goDeeperForUpSync(StackDataProvider.java:129)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.providers.BoardDataProvider.goDeeperForUpSync(BoardDataProvider.java:179)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.SyncHelper.doUpSyncFor(SyncHelper.java:125)
    at it.niedermann.nextcloud.deck.persistence.sync.helpers.SyncHelper.doUpSyncFor(SyncHelper.java:104)
    at it.niedermann.nextcloud.deck.persistence.sync.SyncManager$2$1.lambda$onResponse$0$SyncManager$2$1(SyncManager.java:249)
    at it.niedermann.nextcloud.deck.persistence.sync.-$$Lambda$SyncManager$2$1$B5Glge0jtjic-sLIZD8UEHJ-hfQ.run(Unknown Source:6)
    at java.lang.Thread.run(Thread.java:929)

[desperateCoder]

Ok, thanks for the report, I'll have a look!

[desperateCoder]

This seems to be a very weird constellation... logically this schouldn't be possible to happen, but somehow it seems there is a way the data can get corrupted this way, so it fails at that point.

I added a check on this, the error shouldn't occur any more. The fix will be shipped with the next update.

I'm closing this, because it should be bulletproof now. If you encounter any further issues, feel free to reopen it!