cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging problems SAP Asset Manager 2105 Visual Studio Code

BjörnB
Participant
0 Kudos
550

Hi all,


i am developing for SAP Asset Manager in different version (2010, 2105, 2110,...).
Since a few months it is very hard to Debug the SAP Asset Manager on the Android Tablet and since the code migration from 2105 to 2110 it is no more possible to debug.

I have also created a ticket for the question, but also wanted to ask the community.

SAP Asset Manager 2105:

  • We have created a own built for 2105

    • Used versions:

      • MDK-Plugin SDK (extensions) --> MDK_PLGN_AND00_2-70006391.ZIP

        • Support Package MDK PLUG-IN SDK AND 2105

      • Asset Manager Branding SDK --> ASSTMGRBRNDSDK00_0-70006355.ZIP

        • Support Package ASSET MGR BRANDING SDK 2105

      • Asset Manager Metadata --> ASTMGRMETDTA00_0-70006354.ZIP
      • MDK Client --> MDKCLNT02P_3-80005972.ZIP

        • Mobile development kit client 5.2.3

        --> The application works fine, but debugging is not possible anymore

    • Visual Studio Code:

      • Version: 1.62.3
      • NativeScript - newest
      • MDK - newestPlugIns:
      • Added a workspace with two folders:
      • --> SAM2105_Component
      • --> SAM2105_Metadata

launch.json:
{
"name": "MDK Launch on Android",
"type": "MDK",
"request": "launch",
"platform": "android",
"sourceMaps": true, "appRoot":
"/XXX/SAP Asset Manager/SAM2105/Build/SAM2105_AND/MDKClient_SDK/AssetManagerS19And",
"watch": true
},
{
"name": "MDK Attach on Android",
"type": "MDK",
"request": "attach",
"platform": "android",
"sourceMaps": true,
"appRoot": "/XXX/SAP Asset Manager/SAM2105/Build/SAM2105_AND/MDKClient_SDK/AssetManagerS19And",
"watch": true
}
==> I have connected my Android Tablet by USB-Cable

Most of the time it worked ONE time for debugging by "Run and Debug" --> MDK Attach on Android
--> Earlier this year it ALLWAYS worked with "Run and Debug" --> MDK Launch on Android (This does not work any more), here after saving the app starts new and debugging is almost possible (good solution) but no more possible.

Does anybody have the same problem and a solution for it?

Regards

Björn

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

bjoern.burandt

Were you able to resolve your issue? If any of the below responses helped you, then please mark the helpful answer by accepting it OR post an answer so others might benefit from your findings and then close this discussion.

Regards,
Jitendra (SAP Community Moderator)

Accepted Solutions (0)

Answers (1)

Answers (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

If you are migrating your metadata code from 2105 to 2110 then you should also be using the MDK 6.x client and associated dependencies in your environment.

If you are going to stay with a branded MDK 5.2.3 client then you should not migrate your metadata.