[Bug] Welcome wizard is not usable in Jelly2 screen size

[Pekkari]

Describe the bug

Hi,

I just installed the application in my Unihertz Jelly 2, using Lineage OS 21,
and when I start the application, and start click the initial wizard screen on,
I reach the following screen:

Since it is not possible to scroll down anymore, it is not possible to pass this
screen, and it shows up anytime that I start the application from the icon,
reducing it's usability to when I open a link from other apps.

How to Reproduce

1. Install the app in an Unihertz Jelly2.
2. Start the application and try to follow up the wizard until end.

Expected behavior

The view would be suitable for small screens so that we can click
it through, and won't see the wizard anymore.

Environment

- DDG App Version: 5.224.0
- Device: Unihertz Jelly2
- OS: Lineage OS 21

[github-actions]

Thank you for opening an Issue in our Repository.
The issue has been forwarded to the team and we'll follow up as soon as we have time to investigate.
As stated in our Contribution Guidelines, requests for feedback should be addressed via the Feedback section in the Android app.

[nalcalag]

@Pekkari this is something we're currently working on fixing. In the meantime, you can continue the onboarding flow by switching your device to landscape mode. I'll update you as soon as we release a fix so you can test it on your device.

[Pekkari]

Great to hear, since I have no real hurry, I can wait for your update while using only external apps links, so that I can tell you straight feedback on your fix. Or is there any way to reset the onboarding flow without deleting application data? That way I could use your workaround, and enjoy the app fully, and when the fix come just restore the onboarding and test. Thanks!

[nalcalag]

Unfortunately, there's no workaround to reset only onboarding without deleting app data. I'll ping you as soon as we release the fix. Thank you!

[Pekkari]

No problem, I'm happy to wait for the fix, and try it for you to have quick feedback on it. Thanks again!

[nalcalag]

@Pekkari I'm closing this issue since it was fixed in #5573.