[Archive] [Wallet services] Not enough space between the status bar and the app bar

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by danil.makarenko on 2/27/2024.
This content has been migrated from our previous community forum to preserve valuable discussions.


image
image802×1754 96.5 KB

  • SDK Version: 6.0.0
  • Platform: Android

@danil.makarenko Your feedback has been forwarded to our team.

@danil.makarenko Hi, I have tried example with wallet services. Attaching screenshot with and without appBar. It looks fine.

photo_2024-02-28 12.53.07
photo_2024-02-28 12.53.07576×1280 36.2 KB

photo_2024-02-28 12.53.11
photo_2024-02-28 12.53.11576×1280 34.2 KB

photo_2024-02-28 13.12.20
photo_2024-02-28 13.12.20576×1280 33.6 KB

photo_2024-02-28 13.12.26
photo_2024-02-28 13.12.26576×1280 35.7 KB

@gaurav Could you please try enabling edge-to-edge in your sample app?

@danil.makarenko Pls try refreshing the sdk version 6.0.0 again. Added some changes.

@gaurav
For me, nothing has changed

image
image806×1740 52.2 KB

image
image796×1754 95.2 KB

@danil.makarenko Lets schedule a call in order to understand your code. For me its working. Calendly - Gaurav Goel

@gaurav
Your jitpack repo contains the latest code from 16.02.2024, so your changes are not here.
Please try building a sample not from your repo directly but rather downloading your SDK via gradle.

image
image1364×496 28.1 KB

image
image1106×348 25.3 KB

Can you try using (com.github.Web3Auth:web3auth-android-sdk:-6.0.0-g70ccb6d-1)?

Could not resolve all files for configuration ‘:app:devDebugRuntimeClasspath’.
Could not resolve com.github.Web3Auth:web3auth-android-sdk:-6.0.0-g70ccb6d-1.
Required by:
project :app
Could not resolve com.github.Web3Auth:web3auth-android-sdk:-6.0.0-g70ccb6d-1.
inconsistent module metadata found. Descriptor: com.github.Web3Auth:web3auth-android-sdk:-SNAPSHOT Errors: bad version: expected=‘-6.0.0-g70ccb6d-1’ found=‘-SNAPSHOT’

Hey @danil.makarenko, we have released the new version of SDK 6.1.0 with the fix. Can you please check with the new update?