I am using Twitter and Social framework in my app for iOS. I have been using the same frameworks for days now without any issues. However, today when I run the app in the simulator (haven't changed any Twitter or Social specific code), I get the following error as I try to send a tweet from my app:
Could not load the "TweetSheetLocationArrow.png" image referenced from a nib in the bundle with identifier "com.apple.sociald.Social"
Any idea what's this problem is related to and how can I fix this?
The tweet sheet wants the resource "TweetSheetLocationArrw.png" at runtime from a nib bundle with the bundle identifier specified ( if that doesn't mean anything to you google "apple bundle programming guide" ) and it is either unable to read the resource, or the resource no longer exists.
Ignore it. It's a missing image asset in the device simulator and is harmless.
Related
I'm completely new to React Native, Expo and App development in general.
I'm building a React Native app solely for iOS using Expo. I've finally managed to finish a version I'm happy with, tested with users etc. I've now been spending time adding all the required screenshots, text, info etc to App Store Connect in order to submit the app. While doing that, I learned that iPad app screenshots was mandatory, which I found weird.
I later found that I had "supportsTablet: true" in my App.json file, so it makes sense that it's expecting iPad pictures. After changing this and making a new build and submitting that, it's still a requirement.
After Google a bit I can see that it has been impossible to change this:
Removing iPad support from app
iOS App Submission : remove iPad support
iOS App Submission want to remove iPad support
This led me down the road of trying to upload the app as a new submission. I can't get this to work though. According to this documentation:
https://developer.apple.com/library/archive/qa/qa1623/_index.html
I should change bundle identifier and upload again. Changing this in app.json under expo.ios.bundleIdentifier doesn't work though, as I just get an error that I've already uploaded this app previously.
What are the steps I should do to reupload the app as a new submission, so that I can not support iPad?
In order to upload a new version, you must increase the version and the build number. You can find this if you open the project in Xcode under the General tab and the Identity section. In the same tab, you will see the Deployment Info section where you can untick the iPad. Check the picture attached.
I am trying to build a project that we have previously built many times on a real device through xcode but not it throws a No Bundle URL present error the moment the app boots.
I have tried updating the app, rebooting and updating the info.plist file but nothing seems to change it.
Other apps are booting fine.
I have my info and the error below.
Error Screen
Check whether you are running correct Project. Clean you build folder and then Run .
Seems like this is a common issue for some. I'd suggest checking out this thread with others that had a similar issue - What is the meaning of 'No bundle URL present' in react-native?
I am trying to upload my app to the app store. I can archive my app and successfully upload to App Store Connect, however, it keeps getting rejected with the following error message:
Dear Developer,
We identified one or more issues with a recent delivery for your app, "Retainer Tracker" 1.0 >>(8). Please correct the following issues, then upload again.
ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
Best regards,
The App Store Team
I've tried a bunch of diffrent fixes I've found online but still can't get it to work. Can anyone help?
The basic reason is your application using swift and your swiftsupport folder is empty. Let's move in detail
If your application using Xcode to make .ipa file and there is no third-party IDE involve to create Xcode project, you can fix this issue by upgrading your Xcode
If you are using some other IDE to make the Xcode project then please follow that link. I already give the answer to this question. Invalid Swift Support - The SwiftSupport folder is empty
The problem occurred right after I added a specific Swift Library
Doing the following fixed the issue in my case
Go to Targets > YourApp > Build Settings
Under Packaging:
Defines Module: Yes
Under Assets:
Always Embed Swift Standard Libraries: Yes
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
For us, our CICD pipeline was using an Ad-Hoc Provisioning Profile to distribute the ipa build to Testflight/AppStore.
We fixed this by using an App-Store Provisioning Profile instead.
The title of this question basically says it all. I enabled Crashlytics in my Today extension, and for some reasons, the dSYMs are not being uploaded, even though I'm not using Bitcode.
I tried uploading them manually (from ~/Library/Developer/Xcode/Derived Data/Timelines-evxmjnxmpmcivkavmpijzakaxkrp/Build/Products/Debug-iphoneos/Timelines.app.dSYM), but the web interface doesn't really give me any feedback. It shows this screen:
No matter how long I wait, once I refresh the page, it goes back to the 'upload dSYMS' screen.
I think the problem might be that the UUIDs of the missing dSYMs don't really match those that I found locally.
Some notes on my setup:
Xcode 8.2
Today extension running on iOS 10.2
Bitcode is not enabled.
Fabric and Crashlytics integration was done using CocoaPods.
Archive wasn't uploaded to App Store. I'm just testing it locally on my devices. But since the entry for crash reports was created in the web interface, I assume the automatic upload should work anyway.
My question basically is: how exactly can I upload the dSYMs manually? And, second one: how can I make the automatic upload of dSYMs work? Thank you.
It is described here completely ==> fabric.io.
As it said you can download it from activity tab in itunesconnect and then upload it to crashlytics website.
I'm trying to submit a WatchKit app to the App Store but get this error.
Another cause for this is including a WatchKit or any other TargetApplication.app inside your application bundle.
Do not include any in your project settings > target > Build Phases > Copy Bundle Resources.
A bug in Xcode (6.2..) added it there when I tried to add it to Target > General > Embedded Binaries. Nothing changed in that section and no errors were shown so I ignored the bad feeling it gave me.
After hours dealing with other certificate issues (and hosing all of our TestFlight testers, due to revoking distribution certs, which was apparently/probably required), upgrading to Xcode 6.3.1 I finally remembered this bad feeling and found the app watchkit application lurking in the Copy Bundle Resources section and removed it.
In addition to the Invalid Bundle Structure error above the specific errors exhibited for me were:
ERROR ITMS-90378: "CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.company.App.watchkitapp' under the iOS application 'App.app'
ERROR ITMS-90451: "CFBundleIdentifier Collision. The Info.plist CFBundleIdentifier value 'com.company.App.watckitapp' of 'App.app/App Watchkit App.app' is in conflict with the Info.plist CFBundleIdentifier value of 'App.app/Plugins/App Watchkit Extension.appex/App WatchKit App.app'
All were gone and submission worked fine after removing.
Also, validation passed fine even with both instances of the watckit app.
You cannot submit WatchKit apps yet even though Xcode 6.2 and iOS 8.2 are officially out. See the following answer for more info.