cancel
Showing results for 
Search instead for 
Did you mean: 

Asset Manager - unable to open login page after MDK updated

Radek_Uhlir
Explorer
0 Kudos
243

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:

  • SAM Metadata: 2310
  • SAM Extensions: 2310.0.3
  • MDK: 23.8.7

Current version:

  • SAM Metadata: 2310
  • SAM Extensions: 2410.0.2
  • MDK: 24.7.6

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 -".

 

View Entire Topic
Radek_Uhlir
Explorer
0 Kudos

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

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos
OpenURL function is not used during onboarding. The OpenURL function is only called if used in a rule in the application metadata