I have a UWP Xamarin Forms app that is in the Microsoft Store. I've updated this app in the partner center several times without trouble. My last update was 1/31/2020.
Yesterday I submitted another update but it failed with the following message:
This submission failed with error code(s) 1201
In searching I've come across threads like this This submission failed with error code(s) 2003,1201 which point to problems with Microsoft.NETCore.UniversalWindowsPlatform, but I've not changed that in this submission. Here's a listing of the nuget packages that I changed with this new submission:
Microsoft AppCenter 2.1.1 to 2.6.4
Xamarin.Forms 4.2.0.848062 to 4.4.0.991640
I've also added Xamarin.Essentials 1.3.1
How can I go about troubleshooting this to figure out what the problem is?
Update:
I've determined it is not AppCenter nor Xamarin.Essentials.
Updating from Xamarin.Forms 4.2.0.848062 to 4.3.x OR 4.4.x causes the problem.
In addition, I noticed something I didn't see before: There is a 'silent' error when packaging for the store with Xamarin.Forms 4.3/4.4. This error is NOT present with Xamarin.Forms 4.2.x. The error is:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppXPackage.Targets(3385,5): error MSB6006: "mspdbcmf.exe" exited with code 1106.
It seems likely that the above error is related to the submission error.
Update 2:
I found the following post on the mspdbcmf error:
https://developercommunity.visualstudio.com/content/problem/855376/mspdbcmfexe-exited-with-code-1106.html
I used the workaround described and I was able to get rid of the silent build error but my app submission still fails with error 1201.
Related
After updating xamarin.forms version to 5.0.2244 facing attribute barrierMargin (aka com.example.myapp:barrierMargin) not found myapp.Android\obj\Debug\100\lp\112\jl
res\layout\material_timepicker_dialog.xml 39 and build failed.
We got the same error after updating Xamarin.Forms from version 5.0.0.1931 to 5.0.0.2337:
material_timepicker_dialog.xml(39): [APT2260] attribute barrierMargin (aka com.example.myapp:barrierMargin) not found.
Xamarin.Android.Aapt2.targets(157, 3): [APT2061] failed linking file resources.
After updating Xamarin.AndroidX.ConstraintLayout from version 1.1.3.2 to 2.1.1.2 we could not reproduce this error.
I am trying to run my Xamarin UWP app in debug mode but if fails to open. The error code is
Output window errors
The thread 0x6dfc has exited with code 3221225595 (0xc000007b).
The thread 0x3344 has exited with code 3221225595 (0xc000007b).
The program '[35788] SheepsheadTheGame.UWP.exe' has exited with code 3221225595 (0xc000007b).
I was able to run the app in debug mode and then it just stop working. All my nuget packages are up to date. I have searched the web and tried various solutions other people have had success fixing this issue. I have not been successful.
I have found two lines in the build output window that may be causing the issue.
6>C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.net.native.compiler\2.2.11-rel-30601-02\tools\Microsoft.NetNative.targets(805,5): warning : ILTransform : warning ILT0028: Found native library 'C:\Users\druch\Documents\xxx\xxxx\xxxxx.UWP\obj\x86\Debug\ilc\in\Cosmos.CRTCompat.dll' with unexpected CPU architecture 'amd64', while the current build target architecture is set to 'x86'. Your application may fail to launch. Please make sure to build your application with the matching CPU architecture.
6>C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.net.native.compiler\2.2.11-rel-30601-02\tools\Microsoft.NetNative.targets(805,5): warning : ILTransform : warning ILT0028: Found native library
'C:\Users\druch\Documents\xxx\xxxx\xxxxx.UWP\obj\x86\Debug\ilc\in\Microsoft.Azure.Cosmos.ServiceInterop.dll' with unexpected CPU architecture 'amd64', while the current build target architecture is set to 'x86'. Your application may fail to launch. Please make sure to build your application with the matching CPU architecture.
Could this be the cause of my issue? If so, how do I fix it?
I ended up rebuilding my app (not fun). The UWP app started working again.
When I integrate Firebase with my app, Build failed with an exception.
Although the first error that occurred was a gradle update, i've tried and i still get an error while running gradle.
Because there was no error in the code and the amount of coding was too much, I can only show error messages.
Error running Gradle:
ProcessException: Process "C:\Users\82109\AndroidStudioProjects\instargram_clon\android\gradlew.bat" exited abnormally:
Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details
Configure project :app
WARNING: API 'variant.getMergeResources()' is obsolete and has been replaced with 'variant.getMergeResourcesProvider()'.
It will be removed at the end of 2019.
For more information, see d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getJavaCompile(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
WARNING: API 'variantOutput.getProcessResources()' is obsolete and has been replaced with 'variantOutput.getProcessResourcesProvider()'.
It will be removed at the end of 2019.
For more information, see d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variantOutput.getProcessResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
*********************************************************
WARNING: This version of image_picker will break your Android build if it or its dependencies aren't compatible with AndroidX.
See goo.gl/CP92wY for more information on the problem and how to fix it.
This warning prints for all Android build failures. The real root cause of the error may be unrelated.
*********************************************************
Command: C:\Users\82109\AndroidStudioProjects\instargram_clon\android\gradlew.bat app:properties
Finished with error: Please review your Gradle project setup in the android/ folder.
※ When integrating Firebase with my app, I'm wondering if several versions are all up-to-date. This is because i have optionally and randomly changed to the latest version.
for firebase you can integrate your app manually see firebase documentation
for a quick answer follow this steps:android
Create a Firebase project
Register your app with Firebase
Add a Firebase configuration file (google-services.json)
Add Firebase SDKs to your app
WARNING: This version of image_picker will break your Android build if it or its dependencies aren't compatible with AndroidX => update your image_picker
I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0
With no changes at all to source code or pipelines, I am now experiencing an issue where none of my build pipelines work anymore in Azure DevOps. The package that is being referenced isn't a dependency for this project, nor has it ever been. I can't work out what's causing this or how I can go about troubleshooting.
2018-11-26T10:25:14.2812751Z Restoring packages for C:\Agent\_work\19\s\OrchestrateIT.Web\OrchestrateIT.csproj...
2018-11-26T10:25:14.7577515Z C:\Program Files\dotnet\sdk\2.1.400\NuGet.targets(114,5): error : Unable to load the service index for source https://orchestrate-it.pkgs.visualstudio.com/_packaging/Shared_DBUpdate/nuget/v3/index.json. [C:\Agent\_work\19\s\OrchestrateIT.DataImportScheduler\OrchestrateIT.DataImportScheduler.csproj]
2018-11-26T10:25:14.7577910Z C:\Program Files\dotnet\sdk\2.1.400\NuGet.targets(114,5): error : Response status code does not indicate success: 401 (Unauthorized). [C:\Agent\_work\19\s\OrchestrateIT.DataImportScheduler\OrchestrateIT.DataImportScheduler.csproj]
2018-11-26T10:25:14.7579439Z 0 Warning(s)
2018-11-26T10:25:14.7579628Z 1 Error(s)
2018-11-26T10:25:14.7579743Z
2018-11-26T10:25:14.7579902Z Time Elapsed 00:00:02.18
2018-11-26T10:25:14.7906687Z ##[error]Error: C:\Program Files\dotnet\dotnet.exe failed with return code: 1
Local (manual) build works fine. I have already tried clearing Nuget cache and VSTS agent cache. A quick workaround might be to solve the authorisation issue (even though the package isn't required) however I'm not sure how to go about doing this.
Any advice would be greatly appreciated.
Even though my Personal Access Token had not expired, for some reason I needed to remove and add this package back to my sources with the same PAT. This resolved the authentication issue and therefore resolved the build issue.
It is still unclear to me as to why this package is being considered as a dependency for this project though.