SAP Asset Manager 2105 MDK 6.3.3 - Map on Android not visible

[BjörnB]

Hello,

currently we want to build the MDK-App Android for SAP Asset Manager 2105 with MDK 6.3.3.

We took the Info from MDK Support Matrix, but after creating the Map on the OverviewScreen is always empty and not visible.

The upgrade on a newer SAM version is planned, but we need an update on MDK level to make sure, that the Android Version after 1. November is almost in the Marketplace available.

I have done the Migration for MDK 5.x to 6.x in Web IDE, but this did not help.

Am i missing something? We also tried different MDK versions.

bill.froelich maybe you can help us.

Regards

Björn

[JanarthananE]

Hello bjoern.burandt,

This is due to recent update happened on MDK schema version. please update schema version as "23.4" instead of "6.3" in your WebIDE or BAS and try to build the application deployment.

Thanks,

Jana

[BjörnB]

Hello e.janarthanan ,

thank you for the fast response but it did not fix the issue.

We are using MDK6.3.3 - the migration has also been done on 6.3 - why do we have to use 23.4 in here?

Those are our exact settings for the Build:

- MDK PLUG-IN SDK AND 2210 --> 2210.0.3

- MDK 6.3.3

- SVC ASSET MGR BRAND SDK 2210 0 0700

- Metadata 2105

This error Message we can see right now --> In MDKProject.json we added all the infos:

Regards

Björn

[JanarthananE]

Hello

Inside application-bundler folder there is setting.json file.

Add the @nativescript/geolocation to the externals
PFB

Thanks,

Jana

[BjörnB]

Hello,

thank you for your response once again.

In this project we are working on WebIDE - i added it, but it's also not the solution:

The Screen for the map is almost white and we can't see it.

muhammad.rafay: I have seen you are also familiar with this topic. Can you maybe also give me some support? Jana already gave me some hints.

Regards

Björn

[muhammad_rafay]

Following up on Je.janarthanan comment, there is a setting even in WebIDE to choose which MDK version to choose for deployment so this still applies there.

[bill_froelich]

I would highly recommend using the latest MDK 6.3.x version supported instead of MDK 6.3.3/. If you are upgrading then you should really move to MDK 23.4.4 at this point in time as MDK 6.3 is out of maintenance.

[BjörnB]

Hello bill.froelich & muhammad.rafay ,

thank you for your response.

We currently also tried it with 23.4.x but this also did not work with the map.

So i tried shortly an SSAM 2210 Metadata with the same App-File (MDK) and the map is visible.

So there should be any change in the Metadata of 2105 to fix it.

I now switched to VSCode and changed there the ""mdk.tsTarget": "MDK 23.4+"," --> Deployed to MobileServices --> but the map is almost not visible.

Do you maybe have an example for 2105 for MDK6.X?

Thank you for your help!!!

Regards

Björn

[bill_froelich]

According to the support matrix SSAM 2105 on MDK 23.4.4 is supported using the 2305.0.2 extension controls. This would be my recommended combination to try.

Assuming all your dependencies are in place for MDK 23.4.4, I would start with the branding SDK for SSAM 2305 and take the SAM.mdkproject removing the metadata and replacing it with the base 2105 metadata with the necessary notes applied. Copy in the 2305.0.2 extension controls and create your client. If all is working then add in any customizations and rebuild/retest.

[BjörnB]

Hello bill.froelich ,

thank you for the listing of the versions.

I also tried this right now. The build was sucessful, but the map is almost a white screen.

The target version is set as "MDK 23.4+" and deployed from VSCode.

There is no documentation for the Metadata-Settings of 2105 with MDK 23.4.4 - maybe there is also a migration needed? If i take Metadata 2210 of our demo system, i am able to see the map.

If we look on the MDK Support Matrix everything is fine with the used versions.

Regards

Björn

[bill_froelich]

I assume you also applied the following to your 2105 metadata?

Icons need to be corrected for versions older than 2205 - see SAP Note 3203537

If it still isn't working I would guess there is an additional metadata change needed but the SSAM team will need to assist further on that.

[BjörnB]

Hello bill.froelich ,

yes this i have applied.

So you mean we need to open a ticket?

[bill_froelich]

That would be my suggestion