I publish a maui app with the console command
dotnet publish -f:net6.0-ios -c:Release /p:ServerAddress=192.168.xx.xxx /p:ServerUser=<name>/p:TcpPort=58181 /p:ArchiveOnBuild=true /p:_DotNetRootRemoteDirectory=/Users/<name>/Library/Caches/Xamarin/XMA/SDKs/dotnet/
and this creates an IPA file successfully. However, when I try to upload this file using Transport via a Macbook, I get the following error:
Asset validation failed (90034)
Missing or invalid signature. The bundle 'com.microsoft.libSkiaSharp' at bundle path 'Payload/Istanbul Bridge Conference Application.app/Frameworks/libSkiaSharp.framework' is not signed using an Apple submission certificate. (ID: da574c8d-9ef0-42a9-b7a8-05dfc6df8b41)
In my research I have seen that there are several questions with Asset validation failed (90034) but in all those the asset was the application itself. In my case a Microsoft library is causing problems. The definition of the library says it is multiplatform including iOS, so is this error because of my certificate or microsoft's? Is there anything that can be done to fix the problem?
I'm facing the same problem since the update to Visual Studio for Mac 17.x.
My solution is to copy the file, "Assets.car", from an old archive (built with the old version of Visual Studio) to the new release.
I know that this only fixes the symptom and not the reason, but it helps to get the app into the App Store.
Related
I'm trying to publish my .NET MAUI app using a Mac and I'm getting the following error:
A runtime identifier must be specified in order to publish this
project
First, I'm not an experienced Mac user. Second, I'm on a remote rental Mac and I don't have Admin or Sudo privileges.
With that said, I tried to use the command from Microsoft docs but wasn't making any progress due to a few issues with the IP address of the Mac I'm renting, etc.
I then found a similar issue which suggested that I use:
dotnet publish -f:net6.0-ios -c:Release
Using this produced the error above. Someone suggested I add the runtime identifier to the command so I tried:
dotnet publish -f:net6.0-ios -c:Release -r ios-arm64
This gives me an error that indicates that ios-arm64 is not a valid identifier.
I then tried adding the following to the project file which is still not working and throwing the same error:
<PropertyGroup Condition="'$(IsPublishing)' == 'true' And '$(TargetFramework)' == 'net6.0-ios'">
<RuntimeIdentifier>ios-arm64</RuntimeIdentifier>
</PropertyGroup>
Any suggestions how I can publish this app? I'm just trying to create the bundle. I'll then upload it manually.
If your provisioning profile is correct, and you are using VS 2022, try to export the certificate (p12 file) in Keychain of your Mac and import the certificate and profile into VS.
Go to Keychain, click Login, click Certificates on the top bar, then select the certificate, right click it and export as a p12 file, pay attention to remembering the password.
Move the file to your Windows machine, go to Tools -> Options->Xamarin ->Apple Account in VS, and click View Details, click Import Certificate, import the p12 file and input the password.
Unfortunately, you need sudo in order to publish your MAUI app. I had this issue before and I solved it using sudo command.
I think this issue can be fixed in future VS2022 release or when MAUI officially release in coming November 2022.
I am new in Flutter Development and i have developed an app with Webview.
I have upload an apk on Google Play Store that is accepted but for App Store it shows some error.
Please find below error,
ITMS-90338: Non-public API usage - The app references non-public
symbols in Frameworks/Flutter.framework/Flutter: _ptrace. If method
names in your source code match the private Apple APIs listed above,
altering your method names will help prevent this app from being
flagged in future submissions. In addition, note that one or more of
the above APIs may be located in a static library that was included
with your app. If so, they must be removed.
For this error i have search many things but i am unable found any solution for this.
So please any one who is capable of solving this please help me to resolve this.
Thanks & Regards,
This happens if you are submitting the debug version to the AppStore, Flutter team recommends you to first run
flutter build ios --release
before archiving your app in Xcode.
First make sure you are submitting a release build with flutter build ios --release
If that's not the problem here you could find similar problems related:
flutter build ios --release may use a debug Flutter.framework by mistake
In my case, I updated my Mac to 10.15(Catalina), while the update my cocoapods installation wasn't there. So whenever I try to upload using the command flutter build ios --release and archiving it. Apple sent me the same email you received.
You can install cocoapods using the following commands.
step 1 Open terminal
step 2 command: sudo gem install cocoapods
step 3 set your project path on the terminal.
step 4 command: pod init
I hope it helps.
I building an XAF Winforms App located here following this blog
I am having a difficult time getting my Desktop Bridge application to pass the
Windows App Certification Kit tests
The report states that the App Resources tests fail.
Error Found: The app resources validation test detected the following errors:
The test was blocked from execution. Please try re-running the validation. If the test execution remains blocked then please contact support.
Impact if not fixed: The app might not install if the strings or images declared in your app’s manifest are incorrect. If the app does install with these errors, your app’s logo or other images used by your app might not display correctly.
How to fix: Fix the problem indicated by the error message. See the link below for more information:
App Package Resource Validation
The report also has errors in the Package Sanity Test
Blocked executables
Error Found: The blocked executables test has detected the following errors:File SBD.GL.Win10\DevExpress.XtraReports.v18.2.Extensions.dll contains a reference to a "Launch Process" related API System.Diagnostics.Process.Start
I have tried re-generating the image files and looking through Package.appxmanifest
The help that the error message links to does not contain the error text to look up.
[Update]
I think the issue is related to Nuget installing packages that
I am asking about this at Dev Express
As described in the DevExpress forum, this looks like a false positive from WACK tests. I would recommend to proceed with the submission.
When I build XDK for iOS, I get the message 'An error occurred while building the application. Verify your build assets are correct and try again':
I have searched online and checked the build assets, but can't find anything wrong, so I am stuck.
Is there any way that I can see the log for the build to tell what went wrong? I can't seem to find a link to the logs anywhere, either in the XDK application or the online AppCenter.
OK, I received a reply on the Intel forum to use the Cordova iOS build where there is a link to the build logs.
I was swapping between Cordova and legacy ad-hoc to try to get things working and maybe I got mixed up somewhere along the way. Anyway, I changed two things and it is building OK now with Cordova iOS: -
I found an android setting in the iOS config file that I removed.
I changed the app name, because I read that if it started with the project name that could cause issues.
I have an app in the App Store that I produced using the Adobe AIR 2.0 packager back in March 2011. Now, the client wants to update it. But, I can no longer upload an update.
I get the following error when using the Application Loader:
Unable to unzip application. Underlying reason: Unable to open destination file: /var/folders/05/d7xltrms59j0n1bplx_nvwr0000gn/T/Protocols.ipa/Payload/ProtocolsSmall.app/Info.plist, No such file or directory.
Looking inside the IPA, Info.plist is certainly in there.
I tried using new provisioning and new certificates, I tried using Java 32-bit, I tried reinstalling Flash CS5. I tried the 2.5 SDK (I can't using anything higher though).
I wonder if this packager is creating an outdated IPA that Apple no longer accepts. Ideas anyone?
I managed to solve the problem. I used the AIR 2.5 SDK and PFI. Then, I upgraded Application Loader to 2.4.1 and that did the trick.
To download AIR 2.5 SDK, go to the Adobe archives: http://kb2.adobe.com/cps/853/cpsid_85304.html
To download an updated version of PFI, go to the following link:
MAC:
http://download.macromedia.com/pub/flash/updates/11/ios/mac/PFI_MAC_2_0_1_12640.zip
There is a Windows version, but I can't post that link since I'm only allowed to post 2 hyperlinks.