TestFlight bug type 179 - testflight

I have recently uploaded an app to be tested through TestFlight. The app successfully works on two of the three internal testers' devices, but the third cannot move past the first screen. The error he is sending me says ""bug_type":"179","os_version":"iPhone OS 10.2 (14C92)"}". Does anyone have any idea what this means or where I can start to identify the problem he is specifically having?

Related

Xcode cant recognise iPhone when the VirtualBox MacOS can

so sorry if this has been answered before but I've seen several similar issues but they had fixes that didn't work for me and I don't know what else to do. I have made an app for my Uni work that I'm wanting to get tested by friends via Testflight. I am at the point where I am trying to archive it and I get the errors about no devices or provisioning profiles. Everywhere I looked says if I just connect my IPhone with "Automatically Manage Signing" active this will all be solved. But I just cannot for the life of me get Xcode to recognise phone.
In Virtualbox I have USB 2.0 selected and added the IPhone filter. I have also tried when it was set to 3.0...
In the MacOS the Iphone is detected as a connected USB2.0/3 device. The phone also stops charging as it connects which I assume is good since its connected to a non pyhical machine so cant charge from it if that makes sense...
However the Iphone isn't detected as a device in Xcode
I just don't know why. Is there something I've missed to fix it or a way to manually do the signing as I need to archive the app so I can get started with testflight. Id appreciate any help.

Failed to start remote service on device problem in xcode

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

App rejected due to crash on app store

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.

Xcode 4.3.2 and iOS 5.1.1 + jailbreak: App installs but crash on launch

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.

Why does an ad hoc ipa fail to install on one device, yet succeed on another with the same iOS version?

I have a client whose iPad 2 (iOS 5.0) is able to install an ad hoc ipa, yet his iPhone (also iOS 5.0 -- same exact build) receives the following msg on his device when attempting to install with his Windows iTunes:
"iTunes sync. [app name] failed to install"
I've worked with this guy for a long time testing many versions of this app and he's never had this problem. All his devices install or none. How can I solve this?
As per Trott's suggestion (above), I'm moving the solution from my comment to a bona fide answer so that others can easily find the solution:
Problem solved. Device id was missing from provisioning profile. I'm leaving the issue here rather than simply deleting it bc it might help others. Must add that iTunes used to give a more specific message when this occurred, and since I had not removed the device id from the list in the iPhone Dev Center (have no idea how it vanished) I didn't consider that this cd actually be the cause. Hope this helps someone misled by the vagueness of the error msg.

Resources