In versions, 1.1 and 1.2 app runs fine. I have created a new build-1.1 on Version-1.3. The app works fine in debug mode without any crash when I distributed the app to testflight my app getting crashed.
Note: I haven't Enable Device Specific Build.
I configured the provisioning profile and bundle Id correctly.
Don't know what is the issue. If anyone facing the same issue please answer the question?
It could be a lot of reasons! One way to get to the reason:
When the app crashes, it generates a crash report on the device. Connect the device after the crash to Xcode, open "Devices" window and check the devices crash reports and the console to find out what is happening.
Possible things to try:
It seems like it's a compiler issue. To verify first change the configuration to Release mode and then install the build locally to your phone. You will get to know where exactly its crashing.
Are you using the same Build Configuration (Debug/Release) while debugging on a device and the testflight app?
If not, it could be because of Optimizations being enabled, or unsupported Linker behavior in the iOS Project options.
If yes, try to upload a Debug version of the app into Testflight and retest it
Related
I'm building a Xamarin app, and, so far, I've been able to build without issue on the iPhone Simulator, but I haven't been able to get the app to launch successfully on a physical iPhone device. In the past (about a month ago), the app was working fine on the same device. Here's some background on the specifics:
I develop my Xamarin code on my Windows machine, which is linked a remote Mac (hosted by MacStadium, a third-party hosting service).
My test phone is an iPhone 5c running iOS 10.3.3
To deploy to my iPhone, I build my app in Release mode in Visual Studio, upload the code to a third-party app installation service, Installr, which hosts the IPA file and assists with the installation of my app on the physical device. I've never had an issue with Installr and have no reason to believe that this is the source of my problem.
Since the last time the app worked on the physical device, I updated Visual Studio to version 16.3.2 and updated Xamarin. Here's the Xamarin Specs:
Generally, what happens, is that I download and install my app on the iPhone without any issue. However, when I click on the app, the splash screen loads for about 5 seconds, a white screen briefly appears as follow, then the app crashes.
I've seen several related articles on StackOverflow and other sources on the internet, but none of the proposed solutions see to work for me. For example, I've tried adding [assembly: XamlCompilation(XamlCompilationOptions.Compile)]
to App.xaml.cs with no luck.
I've also played around with changing the CSProj file settings to compile for various combinations of ARM64 and ARMv7. Changing this didn't help either. I've tried changing the linker behavior to "Don't Link" from "Link Framework SDKs Only", and I get an error message stating that the native code is too large for 32-bit architectures. I would compile for only 64-architectures to get around this error, but I believe that the iPhone 5c uses a 32-bit architecture.
Here's what my iOS Project's CSProj file looks like currently. I've tried checking just about all of those checkboxes with no luck:
I'm stumped as to what this could be. Any suggestions would be greatly appreciated. To further complicate things, I haven't been able to get a good log file from the iPhone. Since the Mac is remotely hosted, I can't plug my phone into XCode to pull the logs that way. Does anyone have a reliable solution to get log files another way?
It looks like upgrading solved the problem. Visual Studio was updated to Visual Studio to 16.3.5 from 16.3.2. XCode on my Mac was updated to Version 11.1. After these updates, Visual Studio performed an update while connecting to the Mac remotely.
Our company has a native iOS app that was built in Xamarin/Visual Studio. We originally uploaded it to the App Store a few years ago and have made a few changes to it over the years.
The app itself is very basic. It's basically just a web view that navigates to a Single Page Application. There is very little native app code in the project.
Every week or so I regular launch the native app on our company iPad. Instead of running a version pulled down from the App Store, I periodically rebuild and upload the app from a Mac Mini running Visual Studio and/or debug it directly from the Mac Mini through Visual Studio.
A few days ago I tried launching the native app and after opening it immediately closed. I tried rebooting the iPad but the app still minimizes/closes immediately after opening. If I double-tab the Home button on the iPad, I can see the app still running in the background, but any time I tap on it it immediately minimizes itself.
I tried Cleaning and Rebuilding the native app solution in Visual Studio and re-uploading it to the iPad and that didn't fix it. I updated Visual Studio (and all of its packages) on the Mac Mini, updated XCode, updated Mac OS, updated iOS on the iPad, and nothing resolved the issue.
When I attempt to debug the app from Visual Studio, it shows two error codes in the Output window: MT1043 and MT1007. The debugger always fails to attach to the app as well.
I've tried Googling the error codes and the problem itself and haven't found anything that has worked. I've tried generating a new Development Certificate and Provisioning Profile to use to sign the app when uploading it to the iPad but that didn't work either.
What's strange is that if I download the app off of the App Store it works just fine. The source code that I'm attempting to build/run right now is identical to what it was at the time it was deployed to the app store. What else is strange is that, if I spin up an iOS Emulator and upload/debug against that, the app works just fine.
I tried using a different iPad and it had the same issue. The app minimizes itself immediately after attempting to launch it.
Found the answer. Had to set the system certificate trust from "Always Trust" to "Use System Default". Same solution as provided here: https://stackoverflow.com/a/52506186/9704484
I have an application that i want publish it using application packages file and install manually i don`t want to use Microsoft Store for publishing my app. I create my application package files as you can see below
After that when I want to install my application package from Windows 10 iot Device Portal I didn`t got any error but when application run it stucks on splash screen page.
Generally, if you encountered an app hung up when running, you can follow the below steps to troubleshoot.
Try to deploy/debug the app from Visual Studio;
Try to deploy/debug with a blank app;
Set break points or trace the event log to check if there is some exception or what code causes the hung up.
When debugging with Visual Studio, checked the Compile with .Net Native tool chain in Debug setting, by default, when the app runs in debug mode, it will not use Compile with .Net Native tool chain. Please see this blog.
If possible, you can share the code of your splash page.
When I create a xamarin android blank app template and try to debug the emulator pops up, but the app itself doesn't when I close it it says I have deployment errors I changes the log to debug mode, but I can't find anything wrong (I also read running in administrator mode fixes it but it didn't work for me).
Build Output : http://pastebin.com/gEyY1TZD
Make sure your settings inside the Android Emulator have developer mode enabled and the correct adb settings too, same goes for usb if you use that in the end.
Also, if you're using Xamarin Android Player then try using the main Android AVD Manager to emulate your apps. (and vice versa).
If it still doesn't work, then try using a physical device connected via ADB to then debug the app.
I fixed this by going into that app and enabling developer mode (just like Imdad said) then going to build>>rebuild solution then clean solution. then build >> rebuild "your_app_name" then clean "your_app_name " and then finally going build deploy app. Thanks everyone for helping me out.
I'm having a frustrating issue developing for Windows Phone 8.1 and hoped somebody might have lived through the same thing.
I've had the app running on my phone from a few different deployment packages I created. I recently started deploying directly from VS to my phone when debugging. Everything is working fine. However, when I try to run the app without VS attached, it crashes after the splash screen, with no exception details given. It simply closes.
I've added a handler to the UnhandledException event that will output exception details to a dialog, but this is not displaying anything. The crash only ever occurs when starting the app from the phone.
I reverted to creating a deployment package and deploying that using the tool. However, this version also crashes on start with no message.
Weirder still, I've used one of the deployment packages that had been working fine, and I get the same error: crash, with no message.
I just don't understand this behaviour. Why has an old package that used to work stopped working? I'm using roaming data and considered it might be to do with that, but I really have no other ideas. Please help!