I am working on an app that uses Firebase dynamic links. All throughout testing, the base link, and deep links would open the app, as expected.
At some point, this stopped working on my test device. I tried turning the Associated Domains off and back on again (format is applinks:myappid.app.goo.gl). My URL Types setup in Info has the URL scheme set to my app's bundle id, which is also reflected in Firebase. My AASA still has the expected info in it as well.
I also tried long pressing on the link in both notes and messages (don't get an option to open in app, just open), but it still refuses to work. Oddly enough, it still works in simulator. Any help would be appreciated.
Update: I uploaded the build to TestFlight, and it works properly there. It looks like the issue only occurs on a physical test device, with the app being built from XCode.
Solution Update: Oddly enough after installing a dynamic links build via TestFlight, subsequent XCode test run builds started working properly again. Not the most elegant solution, but at least it is working now.
Update:
This most likely has to do with an open issue that prevents the AASA file from being updated or installed. Currently the only work around is to delete the app, reboot the device, and reinstall.
http://www.openradar.me/radar?id=4999496467480576
Related
Yesterday i was testing my app in the iOS simulator and everything was working fine. I then decided to run the app on my iPhone and i got the error unable to install application, Unknown error occurred this has happened before so I cleaned my build folder (as this has fixed this issue before) however, the same error occurred. I then ran the app in the iOS simulator again and now i get the error Unable to run app in Simulator, An error was encountered while running (Domain = LaunchServicesError, Code = 0). I find this very weird as i didn't change anything besides trying to run the app on my iPhone. I have tried every solution given on this post and still no luck.
I'm sorry if my question doesn't contain much detail but as I said I didn't change anything and it was building and running fine a minute before plugging in my iPhone and trying to run it on there.
Any help would be much appreciated.
edit
I tried running other projects (with and without extensions) and they are working on both simulator and iPhone, therefore the problem must be within my project. (my project does have a today extension)
In that kind of cases I usually :
Product > Clean
Close xCode
Delete the Derived Data (in ~/Library/Developer/Xcode/DerivedData subfolders)
Delete the app on the iPhone
Reboot the iPhone
Restart and rebuild
I had this problem. In my case, it was caused by the Build value being blank. After putting a value there, and resetting the simulator once more, the issue went away.
I had the same problem and checking the system log carefully helped me to identify a coliding library that was causing this error. You can also check this answer if you are using extensions.
Generally it means there is a problem with the build, it may be due to old cache (solved by a clean build) or a project definition error (missing library, bad definition in info.plist, etc).
In my case it happened only on iOS 8, turns out that my widget had the wrong bundle ID.
I've been developing and uploading apps for some months. Whenever they needed being uploaded to the app store, I could do it without problem, but now, I'm stuck with one that doesn't want to be validated/uploaded. XCode says "the request timed out" after MANY minutes with a spinwheel on screen.
The differences between my old updates to the app store and the one I'm trying right now are:
-Xcode 4.X before, Xcode 5 now.
-I had to recreate the app store certificate/provisioning profiles, because they just expired.
-I inherited this project from other coworker (not here anymore) and maybe my "developer profile" is somewhat conflicting with some certificates, etc... (Still many dark areas for me).
I've kind of tried "everything". Erasing provisioning/profiles, closing Xcode, resetting, cleaning my project. But no luck. My current Xcode 5 is able to compile my app perfectly, I'm even able to select the distribute option before uploading (the app is ready to be uploaded onto itunes connect), I even login with my client credentials onto itunes connect, I can even select the correct provisioning profile (app store profile, not a developer one), but no luck:
If I choose to upload or validate, Xcode just complains with some kind of "dull" timeout error.
Any hints? Any way to debug what happens behind the curtains?
Greetings, I'm at a loss.
EDIT: Apparently, the timeout failing event appears in the validation process. If I try to upload, the status log says "Failed Validation". If I try to validate, obviously there's also a "Failed validation" error. Where can I find some log to see what part of the validating process is failing?
Well, apparently: "Problem solved".
After 2 boring days trying to upload my app (via Xcode 5, and via Application Loader), I've discovered that Apple upload servers seem to be overloaded (unless a better explanation arises).
I'm in Europe, and from 9 to 14 h my app was ALWAYS rejected. But once I tried it after 16h, the upload and validation processes worked like a charm (both with Xcode 5 and with Application Loader).
Why this? No idea, but I didn't change anything in my upload process, so it's sad, but the solution is:
"Have patience, and wait to upload your app on a time slot where Apple upload servers are not overloaded". The sad part is: No one knows WHEN is that time :)
I solved it by switching Internet provider.
I simply connected my laptop to my iPhone via Personal Hotspot and used LTE network to upload the app.
It worked for me twice.
for Xcode 13 and Mac OS Big Sure
Install the "Transporter" app from the MacOS app store.
From Xcode's organizer, select your archive and press "Distribute App"
Instead of "Upload", select "Export" and proceed as usual.
Drop the exported .ipa into the transporter and press "Deliver".
In my case I changed the dns server from my provider to the google dns server (8.8.8. and 8.8.4.4).
I think you can try any other, if your providers dns or what ever doesn't work
Faced the error many times, not sure why.
Try this
Export the ipa after the archive
Add and upload in Transporter
I get 100% success in uploading and feel a little quicker than Xcode's upload.
I actually called Apple Developer Support about this and they solved the problem!
It turned out that my recovery email address in my Apple ID (not the main email address but the recovery one) was not verified. They had me go to http://appleid.apple.com, login with my Apple ID, and then go to the 'Password and Security' section (on the left).
After answering my security questions I was able to resend the verification email, and once verified I was able to log in on Xcode straight away!
I have the observation that with Mavericks and App Nap enabled, a hidden Organizer window within XCODE will cause the network connection to be dropped.
Even if the window is occulated (hidden) for just a second).
Make sure the window is always visible and the problem does NOT occur.
Recently, after upgrading to Lion and Xcode 4.2.1 I am getting this error when trying to run my app on my iPhone 4S:
"The application bundle does not contain a valid identifier."
My identifier is indeed valid, and I have been able to run my app with this identifier earlier.
The problem might appear when I change computers.
I have two computers that I am using to code my app, and I am using Dropbox to keep track of my files.
Restarting XCode, my mac and my iPhone does not work.
Cleaning the target and rebuilding does not work.
The only thing I have been able to do to fix it is to create a completely new project and moving my files. This made things work until I swapped computer. Now I am in the same trouble again.
Any idea? Anyone?
Three suggestions:
Check that your developer key is in both computers
Did you try to update the project? There is a strangly-named key in the middle bottom under the project's properties. Try this.
I had similar issues. I found that some things weren't updated when I updated osx and xcode. To get out of the situation, I would suggest creating a new project and copy paste code, files and build settings. This might seem stupid, but you know apple is not good at creating IDE's. You might just get your self lost in the undocumented settings.
Application Settings.bundle contains a version number, which is automatically generated during build. From build log I can see that new value is written there, also when looking inside the file itself in MacOS X Finder I see correct updated value.
Settings in iPhone simulator or in real iPhone shows me the old value. Removing application and reinstalling is so far the only way I've managed to get the new updated value visible.
Question: how can I force iPhone Settings application to read my new latest updated bundle file?
Some background info, which might or might not be related: I install application only via Xcode into both simulator and iPhone. Is this the problem? Just found this in Apple docs, not sure what it actually says. Seems to contradict itself (last chapter)...
Each time you reinstall your application, iPhone OS performs a clean install, which deletes any previous preferences. In other words, building or running your application from Xcode always installs a new version, replacing any old contents. To test preference changes between successive executions, you must run your application directly from the simulator interface and not from Xcode.
So Xcode always replaces old content, but to test changes I cannot use Xcode? What was that? Done both (after installation via Xcode) and didn't see new values in settings. Any ideas how does it actually work? Do I always have to make non-Xcode installation?
Try cleaning and building. It seems that xcode caches dates and doesn't notice the change that your script is making. I've had similar things happen, clean always fixes it, but it is indeed a nuisance.
Make sure to shut down the Settings app running in the background on device. It looks like Settings caches settings while it's running - but pulls the updated values when the Settings app is re-launched.
In my case, it seems that my modified root.plist, created/edited via the Xcode property list editor, just wasn't being saved.
There was no problem at all with the Settings Bundle being copied over to the iPad. A quick cmd-S followed by a rebuild and go/debug updated Settings on the iPad straight away - no app uninstall/reinstall even needed. You'd think there'd at least be a haven't-saved-it warning from Xcode, as there always is for code source files.
I just tried this and it worked.
In Xcode go to : Window->Organizer,
then view installed apps on the connected iPad/iPhone, remove the app, then recompile and run your app on the device.
I think the issue has something to do with the iPad's cache.
I set up all my certificates and keys today and am trying to run my project on my iPhone.
I'm encountering this strange error:
Your mobile device has encountered an unexpected error (0xE800003A) during the install phase: Verifying application
Poking around the Apple Developer forums, I've attempted to set new certificates and provisioning profiles as well as editing Info.plist, but no matter what I do I can't seem to run the app on my device.
The only think I can currently think of is that my project name in Xcode differs slightly from my development provisioning profile (it uses a question mark), but I've named it according to Apple's conventions: com.mycompany.myapp, so I'm unsure if that's the problem.
Any ideas?
Edit: I've hard restarted the phone, rebooted Xcode, cleaed my targets, set up a new wildcard App ID and respective provisioning profile and still nothing. Any other ideas?
It turned out that I had 2 certs in keychain that were simultaneously overwriting each other! I hope this helps people in the future.
You should create a wildcard app ID; com.mycompany.*. That may help.
I've encountered this on many occasions. What i do is clean all targets, shut down xcode, and hard reboot my phone.
This is a different error than the more common problem of getting the cert wrong...
Restore the phone (using the XCode Organizer to reload the latest OS), to be safe do not restore from backup when you sync with iTunes the first time (it'll still keep your number when you sync even if you don't use the backup). I've had to do this a very few times, the last one was when it was in the middle of deployment when I unhooked the phone from the cable (had to answer a call).
Try the reboot (of the phone) first, hooking it up with XCode off. But if that does not solve things, restore is the way.
The console tab in the XCode Organizer sometimes gives helpful hints as to what happens during the install phase. In one case my problem was my app already existing on the phone. I deleted my app and the install succeeded.
Regardless, it looks like a lot of error messages are bundled into this one cryptic message and to really diagnose what is going on, I found the Console tab very useful...
One other thing to try is reinstalling the iPhone SDK. I ran into an error like this when I first got my developer key and this was the only way around.
Just want to say to everyone, when you go to edit Targets-> be sure to set "configuration" in the top left corner to "All Configurations" or the correct config you are building for (Debug or Release). You might think you have things set correctly but it will be for the wrong configuration.
I've seen that error on a correctly provisioned device that has had success installing apps from XCode before, and I've had luck restarting the device and trying again. Maybe that will help.
Try running in Release mode instead of Debug. I have a working project with this problem. No idea what the issue was, but running it in Release mode works, but Debug mode produces the error code.
I have a support ticket open with Apple dev support for the same problem, and (FWIW) I'll post their recommendations if and when they can get my toolchain working.
Try this: (source: http://ephemera.lifewithalacrity.com/iphone_development/)
Even though this is supposedly only for Distribution builds, it helped me to be able to install my Debug version on my iPhone again, after it mysteriously broke yesterday.
"just triple check that all the code signing in your project properties are clear or default"
Note, this is the PROJECT properties as opposed to the TARGET properties. I set my Code Signing Provisioning Profile back to the default and removed the Code Signing Identity string.