Installation of phonegap windows unsigned .appx freezes at 16% - windows

I've try to install a unsigned phonegap windows app in my w10 desktop but the installation freezes at 16%.
I precise that : this native windows app has been developed with "ExtJS" framework and has been built with "phonegap build" without any microsoft developer key at this time. The android and iOS apps work fine.
Would you know the reason of this issue ? Would you think that this could be related to the developer signing key missing ?
You will find a screenshot of the installation interuption.
Thanks you in advance for your help.
Enzo.

I have had issues with deployment on Windows 10 Phone, but it was OK on Android and iOS.
In my case, there were two issues.
1) Wrong architecture
- I was building for the wrong architecture. Changing this allowed me to install correctly.
2) Retina.js
- Once installed, the application would crash. The crash was because Retina.js was being used and Windows did not like it. I do not know why. I removed it, and it worked. So try removing JS libraries one at a time and see if it works for you.

Related

Xamarin.Ios App terminates while starting (in Simulator and iPhone) only stating "The App has been terminated"

I am developing a Xamarin App for Android and iOS on windows. For iOS compiling, I pair with a Mac Mini.
I was forced to update MacOS, XCode, VisualStudio for Mac and therefore Xamarin. On Windows I also updated from Visual Studio 2015 to 2017.
After the updates, Android version works still fine.
The iOS App pairs, compiles and provisions successfully, but whe the App starts (either on simulator or real device), it shows the launch screen and after a few seconds quits back to home screen. It even says "successfully launched" but then terminates
The only logs I get are:
"The app has been terminated" -> on windows, in Debug Window
"Service exited due to SIGABRT" -> on mac, in simulator log file
I searched the web and tried lots of stuff:
Delete obj and bin folders
Clean, Rebuild, Restart VS, Restart Mac, Restart PC, Restart....
Deleted all Provisioning Files and Certificates, recreated them
Used Automatic provisioning, used Manual provisioning
Debug and Release Configuration
iPhone Simulator and Real Device
Sadly nothing worked and I cannot get more info why this happens.
Does somebody have or had the same issue and found a solution? Do you have suggestion what more I can try?
I would really appreciate any help.
Thanks
Edit:
As requested, a Screeshot of my build properties:
I am having the same issue. Restarting the device seems to be the only thing that works, but it's unreasonable to have to restart the device every time I want to run the debugger.
So I finally solved the problem...
I created a new iOS-Project from scratch, added the existing Xamarin.Forms project and copied the files from the original iOS project one by one. I also downgraded all firebase plugins from 5.x versions to the highest 4.x versions and xamarin forms from 3.x to 2.5.x and now the app runs in the simulator and bundle signing works also.
Thanks for your help, I hope my answer will help anyone with similar issues

how to add windows phone emulator to the uwp project

Now I'm updating someone's UWP project.
I use Visual Studio 2017 on windows 10 64bit.
Building is successful.
But When I run this project, I got an error.
DEP6200: Bootstrapping failed.Device cannot be found.
SmartDeviceException - Deployment failed because no device was
detected.
I think, the reason is that I didn't use real windows phone.
So that I wanted to use windows phone emulator.
But I don't know how to add emulator to running option.
When I created new UWP project, I could find emulators which are connect to that project.
Anyone solved this issue?
You have to install Emulators.
Please take a look at this page and download them Windows Emulator archive .
Simply choose your emulator version that you want to debug your app and then Click INSTALL EMULATOR , After installation Restart Visual Studio .
To use emulator there are some prerequest, you can check it from here.
That's to say, first ,you need to make sure you followed the system requirements.
Then you have to install emulator like MKH said. And at last, set the CPU to ARM and choose the emulator you need, run the project and you will see the result.

Issue with Fabric Unity setup. Cannot get past 1st step

I've been trying to setup Fabric on my unity project for analytics and fastlane, but it will not get past Step 1 of the setup.
I have Unity 5.6.3f1 and the plugin installation got through without a hitch on Unity, but it's like the dashboard will not recognize the installation.
I also installed (and reinstalled multiple times) Android Studio with the Android SDK and still nothing.
As per the instructions from Unity, I Built my prototype and ran it on my phone and it worked OK, but still no progress on the Setup.
The Android SDK and JDK point to the correct file path on Unity's preferences as well.
I wanted to try to reinstall the Fabric plugin, but the uninstall instructions on the site's knowledge base is only applicable for Macs and I use a PC. I don't have an option to "quit fabric" nor does it appear in my Android SDK plugin list.
I'm not too sure what to do next.
If I'm missing any info, please let me know.
Thanks!
Edit: forgot to add the screenshot
Screenshot: https://imgur.com/a/JOQuP

Basic Android App not working on Xamarin Android Player via VS2015

I have been trying to run basic Android App provided by Visual Studio 2015 via XAMARIN Android Player. Program gets build and deployed successfully, yet, App or anything does not appear on screen. Xamarin Player takes more than 20 mins to start and then nothing happens. Find Screenshots as well.
WIthin the Android SDK Manager look under Extras there is an package called Intel x86 Emulator Accelerator (HAXM Installer). Installing HAXM will increase the speed of the emulator when you use the Intel Atom CPU/ABI
Also when creating the emulator device check Use Host GPU for increaded performance.
I ran into few issues with Xamarin Android Player as well. Currently I am using Genymotion Emulator and it is much faster.
Well, Well, Well, I got my thing up and running. Following are the steps I performed:
After installing Xamarin for VS2015, I checked for latest Android SDK via SDK Manager. Got all the necessary updates installed.
Installed Xamarin Android Player and used emulator Nexus 5 KitKat API level 19.
Earlier I was using Nexus 5 Lollipop, was the reason why, it was not working. May be its not fixed for buil yet.
As, described by Mr.Pilatus in above answer, the particular HAXM things surely does help in accelerating emulator.
Got my Android app running.
Thank you all for all the necessary suggestion and guiding my in my baby steps in XAMARIN development. Gracias. NAMASTE!

Strange windows phone app crashes only from the store

I am trying to update a 7.1 app from the store. For some reason it crashes only when installed from the store and only on 7.1 or 7.8 devices. My Lumia 920 with the latest updates works fine. The app runs fine if installed from VS 2010 or VS 2012. Of course all emulators worked fine. I put a Messagebox at Application_UnhandledException and it displayed this:
The type 'MyApp.MainPage', specified in the x:Class of
'/MainPage.xaml' could not be found in any loaded assembly.
Of course the MainPage class is there.
The app uses GPS and bing map and has capabilities:
ID_CAP_LOCATION
ID_CAP_NETWORKING
Can anyone shed some light on this?
I have just solved a similar problem where I had this error message when running from Visual Studio on my phone but not in an emulator. My problem was that I had different versions of the Microsoft.Live Assemblies in my 'main' app and the Assembly which contained the 'MainPage.xaml'.
I had a weird issue where my app worked differently from the store than on my device and the emulator. In my case it was because of trial mode. Apps run as though they are purchased when deployed to the emulator or device. It worked on my device from the store too, but that's because I bought it. Any other device which had not bought it ran in trial mode, and that's why it worked differently. I am betting that is why you are experiencing this crash. If it is not then we'll need more information.

Resources