Content from the Content Provider is not loading

[jo-elimu]

How to reproduce:

1. Install the latest version of the Content Provider: 1.2.29-SNAPSHOT (ai.elimu.content.provider.debug)
2. Download all the content (including the storybooks).
3. Install the latest version of the Vitabu app: 1.1.6-SNAPSHOT (ai.elimu.vitabu.debug)
4. Launch Vitabu, blank screen. Should list storybooks.

[tuancoltech]

@jo-elimu Are you testing on main of both content-provider and vitabu?
With debug build of content-provider, the content url path is http://eng.test.elimu.ai/rest/v2/content/images,
and this is unreachable with and without https.
We have to test on release build, using http connection.

[jo-elimu]

@tuancoltech I manually changed the domain from https://*.test.elimu.ai to http://*.elimu.ai.

[tuancoltech]

@tuancoltech I manually changed the domain from https://*.test.elimu.ai to http://*.elimu.ai.

@jo-elimu Just to confirm, were you able to successfully download story books and images?
Upon successful downloads, the number of books/images downloaded will be shown on the UI of the content-provider app.
If you were, then the issue you're observing is exactly the same one I solved here: #105

PS: From your screenshot, I guess you weren't able to download any story book.

[jo-elimu]

@tuancoltech Hmm, seems like the bug is only happening on one of the two devices I'm testing on.

With another device running Android 14 (API 34), the storybooks are being loaded correctly:

Content Provider

Vitabu

[tuancoltech]

@tuancoltech Hmm, seems like the bug is only happening on one of the two devices I'm testing on.

With another device running Android 14 (API 34), the storybooks are being loaded correctly:

Content Provider

Vitabu

@jo-elimu It seems there's an exception while downloading storybooks in your defected device.
Maybe you can look at the stacktrace?

[jo-elimu]

@tuancoltech Yeah, the main difference between the two is that the device that is failing is running Android 15 (API 35). Maybe there is a difference in how Content Providers work between Android 14 and 15. I'll do some more debugging.

[tuancoltech]

@tuancoltech Yeah, the main difference between the two is that the device that is failing is running Android 15 (API 35). Maybe there is a difference in how Content Providers work between Android 14 and 15. I'll do some more debugging.

@jo-elimu Yes please, I don't have Android 15 here so it's better if you can look into it.

[jo-elimu]

I can no longer reproduce this, so closing the issue.