Build of MDKWebpackFactory failed for SSAM 2310

[kevin_karani]

Hi @bill_froelich/@zhen-kun_li/@muhammad_rafay,

I am unable to deploy the SSAM 2310 metadata to the Mobile services. I get the MDKWebpackFactory build failed message.

Build failed.
Please follow the relevant troubleshooting tips below:
ERROR: "Unable to find local grunt"
- Right-click the project folder, select "Clean npm Folder", and build again.
ERROR: "npm ERR! code EINTERGITY"
- Delete the "package-lock.json" file from the project and build again.

I have no package-lock.json file created in my folder. Is there any config setting I am missing.

I am working in WebIDE currently. We are using the Neo Envronment for Mobile service deployment.

Region is Europe (Rot). I have restarted and cleared all browser cache still facing issue.

I have opened in incognito window also we getting the same build error.

Kindly help on how to proceed.

[zhen-kun_li · Accepted solution]

Hi Kevin,

Sorry for the issue. It was caused by typescript upgrade from latest mdk-tools.

Please follow below steps to make it work:

1) delete package-lock.json from MDKWebpackFactory

2) change "@sap/mdk-tools" to 1.9.0 from package.json

3) redeploy your project SSAM 2310 

regards,

zhenkun

[kevin_karani · Accepted solution]

Hi zhenkun, The issue is now resolved by updating the "@sap/mdk-tools" to 1.9.0 from package.json.

[kevin_karani · Accepted solution]

There is one more query though, I now want to have my own Branded Client so do I need to update my npm to higher version(10.6.0)?

[bill_froelich · Accepted solution]

@kevin_karani For creating a Branded Client you should make sure to run the MDK Dependency Installer and verify your local environment configuration. Are you on Windows or Mac and are you trying to build for iOS or Windows?

[kevin_karani · Accepted solution]

Hi @bill_froelich,

[kevin_karani · Accepted solution]

Hi @bill_froelich, I am working on Mac and tring to build for iOS and Android. I have used the MDK Dependency Installer and verified the local environment. The npm used is 8.5.3 and the build works with the MDK Installer.

[kevin_karani · Accepted solution]

Hi @bill_froelich, I have run the MDK Dependency Installer and verified in my local environment and build works fine, I think only the metadata for deployment had the changes to be made.

[bill_froelich · Accepted solution]

If the build is working with your current npm version then no need to upgrade. Especially if the dependency installer shows all is good.