4 weeks ago - last edited 4 weeks ago
I updated extensions and MDK to the newest versions. Now when users want to start onboarding, the login page does not open. Users open the application, aggress to EULA, press Get Started, scan a QR code, confirm the URL, a loading indicator appears and the previous screen with the Get Started buttons opens again.
Previous version:
Current version:
I am sure I am using the right SapCloudPlatformEndpoint URL. The problem is the same when using configuration from BrandedSettings.json or QR code.
Configuration in BTP should be correct. When I try an older build before MDK + extensions update, onboarding works fine.
On a virtualized Android device behavior is a little different. When the login page should open, the error "HTTP Status 400 - " occurs. The web page is opened in Asset Manager in some built-in Chrome window. But the result is the same (Oauth failed).
Edit: I just downloaded all the files for SSAM 2410.0.2 (metadata, SAM.mdkproject, etc), built it with MDK 24.7.6 , and uploaded it to the device with VSC sap-mdk 1.27.0. Instead of the login page "I got HTTP Status 400 -".
Request clarification before answering.
I downgraded to MDK version 24.4.3, where onboarding works OK.
My suspicion is, that in the newest MDK (24.7.6), SAP tried to fix the openURL() function on iOS 18 and broke the openURL() on Android.
https://me.sap.com/notes/3548442 nativescript.utilsModule.openUrl() doesn't work on iOS 18
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
52 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.