On all my test devices and simulators running iOS 11 my widgets failing to load. Just a message in the center "Unable to load". Not visible "Show more"/"Show less" also. Cannot open the app when tap on the widget.
On all iOS 10.x.x devices/simulators everything is fine.
Tried restart devices, delete app and install again from the App Store. Tried remove widget and add again. Tried with new build of the app using last Xcode (9.0), without success.
Any assumptions?
Finally I found the reason..
Here Apple Developer Guide I found this for the widget's plist.file:
"If you don’t want to use the storyboard file provided by the template, remove the NSExtensionMainStoryboard key and add the NSExtensionPrincipalClass key, using the name of your view controller for the value."
So, when I remove NSExtensionMainStoryboard key, works in iOS 11, no "Unable to load" message, the widget looks good, when tap on the widget, my app starts.
Related
I'm running an app in the emulator and am somehow getting the generic error message "Error - Try Again" shown below.
In order to debug this, I would like to locate the UIView corresponding to the "Error" button. Previously, I've worked on the backend for a React Native app and there was the Inspector (cf. https://facebook.github.io/react-native/docs/debugging) with which you could locate React elements in the code.
As far as I can tell from the Help -> Simulator Help menu (see below), there is no such functionality for iOS, or am I missing something?
The feature you're looking for is not officially supported by apple, but there's an awesome tool named Sherlock that enables such functionality on iOS simulator.
It injects itself into the iOS Simulator so that it can monitor views and adjust them in real time and lets you jump into the file related to the view you want to from the simulator.
You can inspect any app in the simulator, including system apps and dynamically change their UI elements!
I'm developing an iMessage app extension on an existing project. When I run it on a simulator it works just fine. But when I try to run it on a device the status says "Running com.apple.MobileSMS on iPhone", the Messages.app opens up on the device and nothing else happens. I also can't find the app in the iMessage apps "drawer".
I've tried to clean the solution, delete the main app, rebuild it again, and nothing seems to help. Also, the executable for the scheme is set to "Ask on launch", but the dialog to select an app isn't shown when I run the app.
I've searched for a solution but didn't find anything similar.
I've managed to fix the problem by reinstalling the Xcode, apparently it was a bug within it.
You should change deployment target in both - app and extension to the same version.
I'm building an iOS app for which I have Testflight set up, but now I'm running into an interesting issue where I can't properly launch the app from Xcode anymore since I registered my device to test the app through Testflight.
When I try to launch the app from Xcode, it will build fine and even launch it on my phone. However, there will be no output in the console, and a few seconds later the app will crash on my phone and I get the following error message popup in Xcode:
process launch failed: failed to get the task for process 484
If I delete the app from my phone before trying to launch from Xcode, the same thing will happen and the Testflight orange dot will still show up next to the app name on the home screen.
I have tried to change the app's version and build number, but that had no effect. I have not yet tried to unregister my device to test the app through Testflight because I would like to find a good way that facilitates both.
One way I have found to circumvent this problem is create a different app target and run the app with that which seems to work -- but I'm wondering if there is an actual solution to this problem or a better way to work around it.
Thanks in advance.
Turns out Max was on the right track - if I manually specify a non-distribution provisioning profile it will work properly by overriding the Testflight version of the app (the orange dot disappears). Not sure why "automatic" wasn't doing that for me. Thank you!
I have an app in appstore containing a widget and it works fine. Now when i tried to give an update for the existing widget and tried over installing through Xcode, the app gets updated , but the widget is not getting replaced with the new version. Please provide a solution.
I had the same problem.
First install a older version
Open it container app, and drop down the today view
Then install the new one
Drop down today view again
It just keeping the old style
After that, I debug the today widget through Xcode
First time, Xcode report a error with some message lick "Lost connection"
Stop debug
Run debug again
The today view drop down automatically and then become the new version style
I wish it would be all right when submit to AppStore just like you said. :(
I tried to download and run the Lister app sample code which was presented at WWDC for the session 406: Integrating Swift With Objective-C. (I am running XCode 6.1 on Yosemite and this is the most updated version of the Lister app from the sample code page in Apple).
https://developer.apple.com/library/ios/samplecode/Lister/Introduction/Intro.html
However I was unable to run the app in XCode which are best show in the attached screenshot.
The app doesn't have the Run and Stop buttons enabled. They are greyed out. Never had this before for any other app.
The icons for the Lister app is not showing. Instead there is this new Settings-like icon which I have never seen and have no idea what it means.
There is a ReadMe.txt file in the project that you downloaded. Have you read it because I had the same problem and by reading it, my problems were solved.
Regards
The QuickStart guide included in the project gives the key setting to change in the Build Settings to enable iCloud.
In the User-Defined section, double-click on com.example.apple-
samplecode to edit the LISTER_BUNDLE_PREFIX value.
Change this prefix to a globally unique reverse DNS string for your own
organization’s name, such as com.somecompany.lister.