We had "Today widgets" that worked perfect for a long time. After introducing the new Widgets Extension we added a Widgets Bundle to our app. Now after every app update the old widgets disappear from "Today view" and can be bring back ONLY by rebooting the iPhone.
Sometime when they disappear, in today view appears the first widget from the Widgets Bundle. I've tested other apps too and it happens every time on apps that support old and new widgets (Xiaomi Home app for example).
Does anyone have a clue how to fix that?
I have rаised a ticket to the Apple Developer Technical Support and I got the following response unfortunately:
Hi Stefan,
Today extensions are no longer supported on iOS. You should migrate to
use Widgets exclusively as the experience you are seeing with today
extensions has no fix or workaround.
Once a Widget target is added to your project they will take precedent
over today extensions and as we mentioned at WWDC, they are an
intended replacement, so you will see the system suppress the today
extensions. I would argue thats seeing the today extensions at all is
actually a bug.
It's a shame that Apple want us to migrate to the useless Widgets that are not even close to the Today extensions functionality.
It might help if everyone affected create a ticket.
Related
We are running into a major issue with building an iOS Widget. iOS Widgets are basically large informational app icons you can pin to your iPhone home screen (What is a widget?). iOS widgets were introduced in iOS 14.
We’ve finished building our iOS widget. However, when half of our users attempt to search for our widget after downloading our app, our widget is not showing up in the widget search results. For the other half, it works fine. This seems to be somewhat of a bug from Apple, as it is affects other widget apps (Apple Thread, the problem exists for large widget apps also). It seems like we are having this issue far more, percentage-wise, than other widget apps. I’ve searched through nearly every resource online (StackOverflow, etc.), which is why I’m posting a question now. Things like deleting the app and reinstalling, restarting the phone, etc. have not been a fix either for these problematic users.
It doesn't seem to be tied to any iOS version (14, 15, etc.). As I have iOS 15, and it works fine. But, some users with iOS 15 are getting the bug.
Has anyone ran into this issue where a widget is not searchable? How did you fix it? Any resources are appreciated as I am at a major blocker right now. Since my app is primarily based on iOS widgets, this makes it basically unusable for certain users.
we have and app in end of life (this year) that we want to update.
We use a really old cordova version, and we don't want to spend 1€ in maintenance.
We updated a label and built the new version but the Apple store block us when we try to publish it.
We used Xcode 11 to build it (we always used xcode 10), could it be the problem?
This is not a new app, why is Apple blocking it?
https://developer.apple.com/news/?id=12232019b
The problem is that UIWebView is now deprecated and you have to update your app to use WKWebView only (via cordova-ios 6+).
There is a big difference when it comes to loading or accessing files with WKWebView, so chances are, you need to spend some time on it.
Read this.
https://cordova.apache.org/howto/2020/07/18/uiwebview-warning.html
You also might need to update your splashscreen is you use one.
I'm implementing a widget in my iOS App. (accessed through 3D-Touching on the App Icon).
However, when tapping anywhere on the widget it automatically opens the App. (The widget still runs all it's functions, but it opens the App when it's done). The widget does not open the app when used as a Today View Extension.
What I want is the widget to run all it's functions without opening the actual main App.
I know that this worked until a while ago, and I feel like the behaviour changed after upgrading to the newest macOS, iOS and Xcode versions. Is there any way to revert the Widget to it's original behaviour?
––––
Upon further investigation I created a new project and added a today extension to it to find out, that tapping anywhere on the widget opened the app (but only when running as a widget, not in today view). Therefore I guess this to be the expected (new) behavior.
However, as long as this is not an Xcode bug I would expect there to be a way of continuing to use the old behavior. If anybody experiences the same issue or found any solutions I would be thankful for any help.
I have an application whose minimum version has been set to iOS 7.0. This application also uses NSUserDefaults dictionary. This application is using UIAlertView and UIActionSheet extensively (not sure how much Apple non-disclosure covers). Now, with iOS 8.0, these two views have been deprecated and have been replaced by controller UIAlertController. Now, there are two ways that I can see which can help me in updating the app for iOS 8.
Raise the minimum version to iOS 8.0 for the update. This way, the users running iOS 7.0 won't be able to see the update. However, it leads to the following situation :-
However, there is one problematic case, and that comes from upgrades
performed from within iTunes or on a device with a higher version
number that is then synced to iTunes. When the user syncs the older
device with iTunes, iTunes will actually delete the application from
the device because it cannot run the new version currently within
iTunes. I had a couple of users with original iPod touches report this
when I upgraded one of my applications to only support 4.0.
The above comment is present under the accepted answer at the following url :-
Raising minimum iOS Deployment Target Version for App Update
Since, the application is using NSUserDefaults dictionary, the relevant entries in the dictionary would get erased when the application is deleted.
The other option is for me to detect in the code which version is being used and code accordingly using if-else statements. This would enable me to keep the iOS 7.0 as the minimum version and might also help me in deploying the update for iOS 8.0. However, this seems like a lot of work which can potentially lead to bugs.
So, I was wondering which option is better between the above 2 ways ? (This application would only be using Objective-C for now due to some constraints).
The best thing to do from the user's perspective is probably to code using UIAlertView and UIActionSheet even though they're deprecated. Keep your iOS 7 target the same as it's been. Xcode shouldn't give you warnings since you're using the older version as your base target. You won't need to change anything about your code and it should still work well enough.
Once you're ready to switch (perhaps when iOS 9 comes out), I would switch your base target to iOS 8 and update your code to use UIAlertController everywhere. To me, it doesn't make sense to spend time trying to support two different versions if it's just an API deprecation that still allows your code to work how you've written it for years. Saves resources and energy to just update it later.
But it's really up to you and how much you want to support iOS 7. I think it doesn't make sense to drop support until the next version comes out. I always try to support the current and last versions so there are no annoyed customers, but it depends on your own needs.
If you have analytics integrated, check out percentage of iOS 8 adoption once it's been released for the public. If not, it's a great opportunity to add it to find out how up to date your customers are!
I'm in the design stage of an iPad app. If I use standard UI elements in my design (e.g. a standard iOS button design) and then get the dev's to implement the standard UI elements without any customization, will they update automatically when iOS 7 update comes out?
If not, what do I need to do when the update comes out? What changes need to be made in the app in order to use the new iOS7 styling?
Short answer : No
Descriptive answer: No they won't get updated automatically. You have to recompile your apps using XCode 5 to make sure that your app looks as per new UI controls of iOS 7. If you won't compile them then you will not be able to see even a single UI component and other than this you might get some crashes too.
It is always recommended to recompile your App and test it according to new iOS version to make sure that your apps looks according to newer UI and doesn't crashes on new OS because of changed/ deprecated APIs
I just updated my iPhone to iOS 7 and all my apps still use the old UI elements, (such as NavBar, TabBar, etc). Not sure yet how to update them to use the new ones, (I haven't updated to XCode 5 for example), but the quick answer is: no, your apps still look the same.