It doesn't work on ARM64

[baoLuck101]

The changelogs for version 6.11.0 mention support of arm64 architecture, but when trying to build a c++ uwp project for arm64 i get an error

When trying to build your c# sample project (publisher_sample_windows.sln) for arm64 i get a similar error

Moreover there is no mention of arm64 architecture in the publisher_sample_windows.sln. Is there any way to use VungleSDK.winmd on arm64?

[gregthatcher]

@baoLuck101 , https://stackoverflow.com/questions/57292495/your-project-file-doesnt-list-win10-as-a-runtimeidentifier-error-when-ru suggests that you edit the .csproj RuntimeIdentifiers section, and then delete the bin and obj files, and restart Visual Studio. Please let us know if that works for you or not.

[baoLuck101]

@gregthatcher, It works for your sample cs project on arm64, but I'm trying to connect vunglesdk.winmd to a c++ uwp project and it didn't work

[baoLuck101]

@gregthatcher, i also get an error when trying to pass the build certification with WACK VungleSDK.winmd has a non-empty manifest resources table.

[gregthatcher]

Sorry about the problems you are having, @baoLuck101. Can you tell us what version of Visual Studio you are using? It looks like Visual Studio 2022 may have had some updates for C++ that might fix your problem https://developercommunity.visualstudio.com/t/warning-MSB8079:-Cannot-read-library-man/10309717?q=%5BVisual+Studio+2022+version+17.6+Preview+2%5D&sort=votes

[baoLuck101]

@gregthatcher , I'm using the latest version of VS. I did some research on test projects and found out how to solve the application certification error. The error text is Every windows runtime assembly must have an empty manifest resource table. Probably, there is <EmbeddedResource> tag in the app.manifest file of the VungleSDK.winmd project. I won't be able to publish my app in the Microsoft store while this tag is in the your app.manifest file. Сan we do something about this?

[gregthatcher]

@baoLuck101 , we don't have any tags in the SDK. If you like, I can try creating an empty manifest resource table, and sending you a new SDK with that change.

Also, please note that in our experience, if the Visual Studio WACK test fails, the Microsoft Store will often accept the app anyway. That is, the Visual Studio WACK test often gives false negatives (the app is rejected) whereas the store's WACK test is much more stable.

If possible, please try uploading to the store (even though the WACK test has failed), and then let me know if you'd like me to create a special version of the SDK with an empty embedded resource file.

[baoLuck101]

@gregthatcher ,

If possible, please try uploading to the store

Unfortunately it is not possible..

When i add something like this to my .csproj file

<ItemGroup>
  <EmbeddedResource Include="res.txt" />
</ItemGroup>

or something like this to my app.manifest file

<EmbeddedResource Include="res.txt" />

i get this certification error. I don't know if there are similar lines in your project and i'd be very grateful if you try to create a version of SDK without them.

[gregthatcher]

@baoLuck101 , we don't have any embedded resources in our .csproj file.

Can you please tell us why uploading to the store is impossible? Have you tried this? In our experience, the Visual Studio WACK tests often fails even though the store's WACK test allows you to upload your app.