Any Nuget for popups in Xamarin.Forms ? Even with the latest update of Rg.Plugin.Popup the popup's are crashing on iOS 13 devices !
Here is the issue
https://github.com/rotorgames/Rg.Plugins.Popup/issues/459
Please close the VS and run
dotnet nuget locals all --clear
in a terminal. After it restart your mac and check it.
Related
I am using Intellij Idea rider to develop xamarin projects. Everything worked normally since 2 day ago when a strange error started to appear when trying to run the app in android emulator. I get this strange error : Error running Android Default: Unexpected schema version 3
In the emulators section of the android project run config i see 0 emulators. I have 5 emulators eligible for running the app. Everything is ok with the emulators because i can run the android app using Visual Studio for Mac. I am using Mac OS Sierra. Any ideas?
Probably, a path to Xamarin Android SDK has changed to a wrong one for some reason. You could check this in Settings: "Rider | Preferences | Build, Execution, Deployment | Android". If it is ok, I would contact Rider support team.
It is a bug in Rider. Fixed in Rider 2018.2 (EAP)
https://rider-support.jetbrains.com/hc/en-us/community/posts/360000540970-Error-running-Android-Default-Unexpected-schema-version-3
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
I have VS2015 and VS2013 installed side-by-side. In VS2013 I have a list of emulators to start my app and it works awesome.
But VS2015 only has device in the list. How do I add the phone emulators to Visual Studio 2015?
UPDATE:
After playing around some more I've dug up some new findings.
Creating a new universal JavaScript project has the same issue
Creating a new universal C# project DOES show a list of emulators.
This worked for me!
Although I had CoreCon\12 and vs2015.3 instead of CoreCon\11 and vs2012
Maybe you could fix this issue by deleting this folder
C:\Users\\AppData\Local\Microsoft\Phone Tools\CoreCon\11.0
Then open VS2012 again.
If not repairing is always recommended
original post : no-emulator-lists-to-deploy-windows-phone-app
Rerun the installer. Make sure that the desired options are checked (probably either Windows Phone 8.1 Emulator or Microsoft Visual Studio Emulator for Android, you don't say which emulator you are interested in). If in doubt, just check everything.
If you had unloaded your start project, it may not be your start project anymore after reloading. So do a right click -> Set as Startup Project and then hopefully the emulators will reappear.
Can I run the Android SDK emulators for Android website testing in Aptana Studio 3?
Do I need to install the Eclipse plugin?
I have installed Android SDK, and use Aptana Studio 3, but I am not sure if they will work together.
Thanks in advance
Ant
I don't see a major conflict by installing both plugins into Eclipse.
Aptana Studio's 'younger brother', Titanium Studio, can run both, so no real reason why the studio wouldn't run both as well.
In any case, if you stumble into issues like that, you can open a ticket at http://jira.appcelerator.org/secure/CreateIssue!default.jspa
Mobile application runs perfectly in the debug mode - I can test it on the device etc... The problem is with the release build - it simply does not run. When I manually install .apk I don't get any errors messages, simply a green check mark and "Application not installed" message. Any thoughts?
Running the latest version of air and Flash Builder 4.5.1
I'm not 100%, but if I remember correctly, you need to uninstall the old application before installing the new one because of a name collision. Try that.
I just ran into this problem and regenerating my p12 certificate fixed it.