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.
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 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.
We are facing some REALLY weird issue with our ios app in React Native. Testers from Apple in United States region are unable to press any button in app (screen with TouchableOpacity and Button component, Node version: 0.62.2.)
The weirdest thing is, that testing in our region (in particular Czech Republic) it works like a charm in every simulator combination of OS/device/country/language and also on our real devices with different operating system. (｢๑•₃•)｢ ʷʱʸ?
Has anybody facing similar issue with React Native and iOS?
We have already excluded these error causes:
network (it works ok it's even sending data)
app crash or exception - nothing logged
wrong import: correct ToucahbleOpacity from react-native
What we see from logs, the difference is only the region, so we are leading this path, but in fact feeling hopeless little bit. ಥ_ಥ
For those who will face similar very weird issues and drown in despair as we did. (ó﹏ò｡)
What helps at the end? We didn't find the exact issue, we couldn't simulate it on any device, but what we did was complete update of React Native, React, Xcode and all libraries and tools related to app. That was ultimate solution, but was necessary. (~_^)
I made a widget based off of the default template. It works on my phone when I run it on that, but when I uploaded it to TestFlight, one of my testers did not get the widget (he has an Iphone 6s). I checked with other testers and it showed up for them, so I tried installing the widget by running it from xcode and it still did not work. It doesn't crash, the app starts up fine except for the fact that it doesn't do anything. viewDidLoad() doesn't get called, along with widgetPerformUpdate().
The app runs fine on his phone, and other testers with a 6s didn't have any issue with using the widget.
Is there anything I can do or is it safe to assume it is a bug on the specific device? How can I troubleshoot this if no functions are getting called?
The only other thing I noticed about the phone is that the charging port was damaged in some way, making somewhat difficult to run the widget without the device being disconnected from xcode. However I am fairly certain I was able to completely run the widget with breakpoints and none of them were triggered.
I have all the editing functionality in the container app of my keyboard extension, and I have a button to open the container app on the keyboard. I was using these methods openURL not work in Action Extension
However, in iOS8.3 apple changed his mind again. And, I cannot find a way to open the container app.
Has anyone any idea how to do it? Please, help!
Apple hasn't changed its mind on this even once, let alone "again". Only today extensions support opening their containing app, others do not. The workarounds that people found were-- from Apple's perspective-- bugs that were fixed.
There is no supported way to do what you want. If you find some workaround, you should expect it to disappear in the next iOS update.