I had developed an app and uploaded it on app store. The app got rejected due to crash. But my problem is that I cannot detect this crash while running app on device for testing. App is working properly on the device.
The app is been created in unity and then I had exported it to xCode.
So I want to ask that how can I get to know about where it is getting crashed. Also how can I traverse the crash log.
Any help will be appreciated
Thanks in advance
Did they tell you about:
– Where crash happened? (At launch, On logging in, or in specific screen)
– Did they send you any images?
– Which devices and iOS they were testing
– They will surely send you crash log, please post it.
You said you cannot replicated the crash, but did you tried with simulator or real devices?
Since you are missing many information, I cannot give you a certain answer. My advice for you is to
1) Updating your question
2) Read my post about how to do when your app got rejected, or my post about how to symbolicate crash log
3) You can also follow the topics in stackoverflow: Iphone App was Rejected Due to We found your app crashed on launch so we were unable to review it and App rejected due to crash. They are very helpful
Actually, app was getting crashed on devices with 64 bit architecture. as older version of unity don't support 64 bit architecture. Unity 4.6.2 onwards support 64 bit architecture. Thus rebuild the ios app and it worked fine.
Related
I'm trying to get my Flutter application to receive messages using Cloud Messaging. This is working great on iOS, but for my Flutter macOS application, no matter what I try it's not working.
There seems to be very little documentation online about how to do this, with even the official documentation not being particularly clear.
What I have tried:
Cleaning Flutter
Removing pods and rebuilding
Sending messages from both Firebase's test page as well as a Firebase Function
What I am wondering if I have got wrong:
In the documentation it says For iOS; you must have a physical iOS device to receive messages., does this mean I should be doing something different when running a macOS app too?
Where it says in the documentation, This guide applies to both iOS & macOS Flutter apps, repeat each step for the platforms you require, does it literally mean every single step, as some steps seem to be fine not being repeated eg....
Can I reuse the same Firebase iOS app and Apple key or do I need to create a separate Firebase iOS app and separate Apple key?
Can I use the same identifier as with my iOS implementation?
Thanks so much!
For anyone else trying this, it turns out that notifications shouldn't work on MacOS using the default build approach. Instead, you must use a notarized version of the app. Many thanks to Markus Aksli, who responded with the following:
No, you can just run on your mac, however you need a build that has
been notarized by apple (https://github.com/FirebaseExtended/flutterfire/issues/5717)
You can use the same identifier and key
I create a flutter app and now I'm trying to run it through XCode on my real iPhone, but after the installation finishes, I face the following problem:
Also with I trying to run the application on my real phone, after clicking on the application icon, I face a white screen appears, and then the application closes directly.
Catalina 10.15.3
IOS 14.2
XCODE 11.7
Also I was make a trust to app in phone
Does anyone know the reason for this problem?
This problem maybe because of two reasons:
First: Xcode 11.7 doesn't have support files for iOS 14 you can download it from here https://github.com/filsv/iPhoneOSDeviceSupport
Second: I have this problem now and I couldn't fix it.. but I have iPhone with iOS 14.2 and iPad with iOS 14 so the problem was just on the iPhone but after I updated the iPad with iOS 14.2 it happened with it.. so the problem maybe because of the iOS 14.2 so we have to wait for the update or because of the Xcode 11 version and we have to download the Xcode 12 version..
I hope we can find a solution quickly...
make sure to have the latest system update on your target device and the latest Xcode version as well. The error should disappear.
Best,
Ralf
I have fixed the problem by using the above solution but it has happened again. So, I have followed these instructions and fixed again:
https://stackoverflow.com/a/61665031/6586109
A good first place to look is Window > Devices & Simulators in xCode, then find the details for your device. There may be error information here that helps you find the fault.
Restarting devices and installing updates seem to fix this problem for a lot of people.
For me, there was a red notice in the device window about connection to the device and it turned out to be the cable that was at fault.
This was an official Apple cable, just a few months old, and still works fine for charging and data transfer; and I've been using it with xCode without problems for a couple of months. It seems to be possible for Apple cables to develop some tiny physical fault that seemingly only xCode is sensitive to.
Using a different cable worked first time for me.
There seem to be a few variations on the exact error message with the same root causes varying depending on exactly what xCode was trying to do at the exact moment it failed: I'm on xCode 12 and for me it was:
Failed to start remote service on device
Failed to start remote service com.apple.installation_proxy on device
I have a problem when trying to test an application on macOS. For reference, this was created in Unity.
The BundleID has been changed as a previous developer had used a very odd naming format, codesign and notarization works on the new app.
However, when I try to run the app it starts complaining about the app being purchased on another computer (which is correct, we still use the old version for testing) but it has been removed on this device and hidden in the App Store.
Anyone know anything else I can try to get past the problem of macOS knowing about the old app version.
If you log in it then just says the app is corrupt as I am guessing it is comparing it to the downloaded App Store version.
Solved it myself, apologies for taking up bandwidth. In Unity untick Mac App Store Validation in Player Settings-> Other Settings
I have my app working to my satisfaction both in the simulator and on two devices when debugging through Xcode 4.3.2. I use OTA Ad-hoc distribution to send to my beta testers. After archiving, saving, and uploading my ipa and plist file to my website, I then download and successfully install the app on my phone.
Sounds good, right?
HOWEVER, I am using CoreAudio and CoreData, and low and behold suddenly there is no sound in my app. I delete and install OTA on the same devices I am debugging with, so I am at a loss to where the problem is occurring.
I have a feeling that there might be an underlying problem with my Core Data model (which feeds my sound) but checks upon checks seem to verify that it is working. It DOES work when I install from Xcode, unplug, close, and reopen the app on the device. Only the OTA install has this problem.
Has anyone encountered any differences in behavior like this? I checked my build settings and the only difference I see for AdHoc is using the Entitlements.plist, which only useful setting appears to be NO to debugging.
I don't have the Apple 79€/year account. In iOS 5.0 and Xcode 4.2.1 I changed SDKSettings.plist ecc... And it works. In iOS 5.1.1 and Xcode 4.3.2 no, I already changed settings ecc but don't work, the app installs on device but crash on launch... How can I run my app on device without crashes? Thanks, and sorry for my english.
I have had this issue before on a jailbroken device. You have a few solutions depending on the exact issue. First you can install app sync in order to allow unsigned code to work on your device if you are not using a valid code signing identity. The second option is to actually get a valid code signing identity along with the provision profile so you can run the application correctly. This involves paying for the developer program so this may not be the best option.
Last is a very common issue with jailbroken devices. Which is that you will receive an error such as "failed to get the task for process xxxxx". This tends to happen a lot with jailbroken devices. This is because Xcode notices you are not using a provision profile that is required to report error logs. All you have to do is launch the application again on the device and everything should work.
This is just Xcode not being able to fully launch your application because of the missing provision profile so it results in a crash. If none of these solutions solve your problem please post a more detailed explanation of the issue you are having.