Why do I constantly get this when i try to run a shortcut with the xfinity stream app. i never had this extra step before.
[Re-Titled by Moderator]
EUREKA!!!! iPad OS 15.1 has solved the null problem!!!
In settings > Privacy > HomeKit I disabled the toggles for the apps eWeLink, Mi Home, Smart Life and Tuya Smart (The shortcuts of the apps which showed this popup in my apple watch)
After that this popup appeared only once and after clicked allow, This annoying pop up stopped appearing for my shortcuts in apple watch.
It should have been resolved on iOS with 15.1 as it was a privacy feature (the toggle needs to be in the privacy menu of the shortcut). However it is still an issue on Apple Watch
First, we are all other users here, so no one from Apple will chime in. Second, Apple made some changes to the OS to ensure the user’s privacy and one if them is that all apps must get your consent to share your data. The only change from the “old days” is that they now have to ask before they use or sell your info if you allow it. They have always been doing it, you just were not aware of it…….. and now you are and have an option not to allow it.
It’s not a bug , it’s a feature and I applaud Apple for caring enough about your privacy to implement it. I never allow any app to share anything because my info is not for sale.
For any developer reading this - I can confirm that this problem doesn't happen if you make sure that you have a watch-specific Siri extension embedded into the watch app. In this case, the Siri shortcuts code will run on the watch itself, and this confirmation alert will not keep reoccurring. This however can cause other problems. If your Siri code requires network access, you will now be running it on a slower and less reliable watch networking, which often goes through a slower bluetooth connection with iPhone. This can be slow enough that the Siri request just times out if your phone is for example behind a wall in the other room. In the case of my app that can have a few network calls for one Siri action, I found it more reliable to have the watch just pass on the Siri request to phone where it will execute and just return the response back to watch, than to run the same network code on the watch. This is also a valid way to do things - in Apple's dev instructions they clearly say that Siri shortcuts code can be executed on the Siri extension in the watch app, and when that extension doesn't exist, the code will be executed on the phone.
The problem described here is not some kind of intended behavior. It s a bug, as the alert keeps reoccurring even after the user repeatedly gives the permission to a shortcut.
makis1985 wrote:
Hey come on Apple ; fix that issue of annoying message “allow xxxx app to share data with null”
make your developers fix the issue Apple
Apple isn’t here. Only fellow users, like yourself.
The best way to get third-party developers to fix their issue is for you—their customer—to contact them, directly.
I just checked on my iPhone. Issue seems to be resolved there as well as my iPad. It asked me to "allow" the first time. After that all was fine. Must be just a watch problem now. I don't use an apple watch. I can see the time on my phone :>)
Did you guys follow my link on r/shortcuts? I solved my issue with Smart Life by applying theapu’s procedure, and also fiddling with “show/don’t show on watch the specific shortcut” on iPhone’s Shortcuts app. Then you rerun from watch, you allow it once when the bugging message appears: end of trouble.
HTH
I FOUND A WORKAROUND!
If you are still having issues with the Apple Watch asking to "Allow to share data with (XXX)", here is how to work around it:
You need to create a New Shortcun that runs the Original Shortcut. How?
I will give it to you, this is pretty circumvoluted. But it works for me!
Hope it does for you too.
[Edit: please note that this Workaround worked with the SmartLife app. I did not test for other apps activated through Shortcuts. I am currently using the latest official software on both iPhone and Apple Watch.]
If there is something a developer can do, I'd love to know it. So far no one on the developer problem solving sites has figured anything out. This issue is happening on the watch to apps where the shortcuts are being issued on the watch, but processed on the phone, which is generally fastest and most reliable approach for watch apps. Problem is, in a setup like that there is nothing for the developer to tweak and modify - it's all done through OS-level communication. One thing worth trying would be to make the shortcut processing happen on the watch itself. I might actually try that tonight and see how it goes, because this problem persists even on iOS 15.3 / watchOS 8..4
Just updated to 15.1 on my Iphone 12. It now looks like it is fixed.
I have the same issue:
You can enable the toggles in settings > Privacy > HomeKit after allowing the first prompt for shortcuts in Apple watch. After enabling HomeKit toggles again Apple watch shows this "Allow to share data with (null)" only once for shortcuts.
May be there is something that needs to be done from the makers of these apps to handle this security prompt? Could that be the reason apple is ignoring this bug?
It will be nice if some one from Apple could provide a clear explanation for this annoying bug. If it is some thing that needs to be done from app developers side please clarify it.
I think I am one of those lucky guys who does not have this bug. For me the disabling and enabling the apps in Home kit section of settings solved the bug for ever. Did not occur even after update to ios 15.2.1
Hope it doesnt break again after upgrading to 15.3.
It would be really nice if someone from Apple actually replied to these things.
"Allow to share data with (null)" with xfinity stream app on iPad iOS 15
