I run a Xamarin.Forms project on Release mode on my device. It's installed on my device. When I share the app to other device, the app is not installed. It shows the error like "App not installed"
Please see the logcat output here:
Can any one please help me to resolve this issue.
Related
First, some informations about the enviroment:
-App built with Xamarin Forms 4.7.0.968.
-Visual Studio for Mac (last version)
-iOS SDK 13.4
-Xcode 12.5 (I've tried also the Xcode 11.4)
-Certificates, Edentifiers and Profiles: All ok.
The problem:
On Visual Studio for Mac I build the project, as release for iPhone plataform and Archive it for publishing. I click on Sign and Distribute, App Store and Upload. When it saves the IPA on my mac and starts to upload to app store I get an erro: "Invalid Toolchain. Your app was built with an unsupported SDK or version of Xcode..."
I also tried to just save the IPA on the mac and do the upload with the Transporter. But, again the same error, as shown on the image below:
The Invalid Toolchain error, on Transporter. Is the same message that shows on VS for Mac
I already readed all what I coud on internet.
OBS: The android version went to play store without any problem. And, I can debug the iOS app without problems.
I converted a hello world javafx .jar into .apk using eclipse, gluon and gradle, I successfully installed it on an android phone, but it's not working, it crashes anytime I try to run it. It shows "unfortunately, MyHelloWorldApp has stopped". Please, how should I fix this?
I am having issue debugging Android project. I can deploy to device and run it, all works fine but if I try to debug, the app gets deployed to the device and very briefly opened, splash screen shows up but the app then closes.
I am using Xamarin Forms on Visual Studio 2015.
Device is running Android Oreo (8.0.0). Another device running Android 6.0.1 is debugging fine.
The output shows following:
InspectorDebugSession(11): StateChange: Start -> EntryPointBreakpointRegistered
InspectorDebugSession(11): Constructed
Android application is debugging.
InspectorDebugSession(11): HandleTargetEvent: TargetExited
InspectorDebugSession(11): Disposed
Couldn't connect to logcat, GetProcessId returned: 0
I checked Logcat and it seem to be having issues finding FFImageLoading library:
Time Device Name Type PID Tag Message
09-18 14:35:52.361 Huawei Nexus 6P Debug 1560 Mono AOT:
image '/usr/local/lib/mono/aot-cache/arm/FFImageLoading.Platform.dll.so'
not found: dlopen failed: library "/data/app/myapp.android.dev-
WEb1bz8edgF7vwx6uCoZ-A==/lib/arm/libaot-FFImageLoading.Platform.dll.so" not found
I have added Nuget package for FFImageLoading to my projects and Droid project references show it as in image below:
This worked for me :-
Deselecting the 'Use Shared Runtime' in Project Properties > Android
Options > Packaging properties
I also had this issue with Android 8.1 and Visual Studio 2017 15.7.4.
There are three steps to got it working again.
Under Android Options, go to Advanced and add your device architecture, in my case it was x86_64.
Go to Tools -> Options -> Xamarin > Android Settings and enable: Provide debug symbols for shared runtime and base class libraries.
And the final step is to delete following Apps from your device:
All Xamarin.Android API Support libraries
Mono Shared Runtime
Your App
After these steps you don't need to disable "Use Shared Runtime" and can Deploy and Debug much faster.
This is a known issue with Oreo and Xamarin Android on Visual Studio for Windows. It works on Visual Studio for Mac apparently. It will be fixed in an upcoming release. In the mean time there is a work around down near the bottom of the bug link above (comment 20).
deselecting 'Use Shared Runtime' in Project Properties > Android Options
delete bin & obj files from solution
clean solution
rebuild the solution it works
One another reason for that is if you dont enable usb debugging on your device, VS 2017 still recognizes your phone and installs the app on your phone. Just after debugging starts, it will throw this error and not continue debugging. Make sure to enable Developer Mode -> Usb debugging like described here
https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/set-up-device-for-development
Using the default Blank Cordova project in VS2015 update 1, I try to publish (Debug > Android > Device) to the Android Emulator (Tools > Visual Studio Emulator for Android) and I get the following error:
Severity Code Description Project File Line Suppression State
Error Unable to deploy to Android device, no attached device was found. If you recently attached a device, you may need to wait a few seconds before it is recognized. BlankCordovaApp2
I am also getting the following error when I click Yes in the pop-up deployment errors window :
Operation not supported. Unknown error:0x80070057
Here's the device list from ADB confirming the VM is being detected.
No luck with the following.
I reinstalled Android SDK Manager and updated files.
I removed and then re-installed VS2015 community.
I can use adb.exe to check for the emulator device and it sees the device.
The android emulator appears to be working and displaying properly.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK is pointing to the correct location
renamed CoreCon
Ran Dependency Checker (Tools > Options > Tools for Apache Cordova)
I can deploy the .apk package on the Android emulator using adb install folder\location\xxx.apk
Any thoughts?
All I had to do was enable Android USB Debug on my phone.
Go to Configuration > System > About the Phone (My Phone is in Portuguese, so the menu options may differ a little bit)
Scroll to the bottom and tap on "Version number" around 10 times
A new option called "Developer" will be available under Configuration > System. Open it
Enable USB Debugging
Deploy the app again
Windows 10, VS 2015, Cordova 6.3.1, Using Andriod 23
I hab some trouble with different adb.exe errors and i fixed all of them. Perhaps this checklist will help. (Some things were already mentioned but nevertheless^^ her is my list):
Make sure yor device is connected to your Laptop. Check this with the console command "adb devices" (you have to be in the directory where adb.exe is)
If you see more than one an emulator is running , kill him (restart pc) if you see nothing check out another usb cable.
DELETE the app from your phone e.g. if you changed developing machine.
When installing MS Visual Studio you can first uncheck all and then only check Javascript->Cordova. Setup will make the rest. But install node.js and andriod-sdk (only sdk not the wohle andriod development studio... no need)
with the Andriod SDK-Manager make sure you have "Andriod sdk build tools" ONLY for your version installed.... for me 23.. AND Extras->"Andriod Suppot Repository" i have it like this:
here you can see my SDK Manager Part 1
here you can see my SDK Manager Part 2
5.Make sure you have developer options activated on phone and USB-Debugging is enabled. And on startup make sure you allow access from the Machine e.g. laptop to your device e.g. phone. A prompt should appear on your device.
cya
I encountered a similar problem.
Solution:
1)Open Developer tools in android devices and Revoke USB debugging authorizations
2)Then restart USB debugging
I was able to resolve this by editing the config.xml file and changing the Target API Level to match the installed version of the Android OS on my phone for development. Here is a link to the google developer docs:
https://developer.android.com/about/versions/marshmallow/android-6.0.html
It contains info on backward compatibility to help with setting the version appropriately.
Here's a work around to my problem. It doesn't fix the original problem, but it does allow me to debug using the Visual Studio Emulator for Android
Work Around:
Use the Debug > Android > VS Emulator XXX in the drop down to open the emulator and debug. VS Emulators can be added by using Tools > Visual Studio Emulator for Android
Previous Workflow:
Open Tools > Visual Studio Emulator for Android
Launch the Device Profile
Wait for the Device Emulator to open
Debug the project by using Debug > Android > Device
Close VS
Open it as Administrator
Tools > Visual Studio Emulator for Android
Start an emulator
Voilá
It worked for me
We just started creating cross platform mobile apps using "Visual Studio Tools for Apache Cordova".
I followed the procedures described in Install Tools to Build for iOS and To run your app on an iOS device. Everything works nicely, the app gets deployed on my USB attached iPhone and runs as expected.
I then tried to upload the app to iTunes, to provide the app via TestFlight to testers and to generally see how app-submitting works:
Build the iOS app as "Release" in VS: it builds and deploys to the iPhone nicely
On the Mac: Start Application Loader, click on "Deliver your App" and navigate to "...remote-builds/builds/"xxx-buildnmb"/cordovaApp/plattforms/iOS/build/device/APPNAME.ipa"
Several checks run OK ("verifying assets, etc.), but it then stops with the error
ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle xxx.yyyyyy.zzzz [Payload/xxx.yyyyyy.zzzz.app] is invalid. [Missing code-signing certificate.] For more information, visit the iOS Developer Portal."
I then discovered the Xcode Project in ".taco_home/remote-builds/taco-remote/builds/<build-number>/cordovaApp/platforms/ios/" and used Xcode to define the code signing identities in "Build Settings" and the Team information in "General", created the archive via Product-->Archive and submitted it in the Organizer - Archives. And voila it worked!
My questions:
Do I have to use Xcode to submit?
If not, what might I be missing in a) regard to building and signing apps with vs-mda-remote, and b) submitting it with Application Loader?
What are Microsoft's plans in regard to providing access the build settings from within Visual Studio (similar to the ones in Xcode)?
Thanks a lot for any pointers in the right direction.
Thomas
You need to use distribution provisioning profile to sign the package and apps are published to the App Store by using the iTunes Connect website along with the Xcode Archive Tool, which is included with the iOS SDK.