Hello, looking for fellow sufferers trying to use the location trigger (still apparently in 'preview') that are getting the cannot be installed" error.
This was mentioned elsewhere and apparently
I received some support by Microsoft on this issue, and it is due to the rollout of the trigger in all tenants (previouslu, it was in preview). So, by now it should work.
It would appear that this isn't the case.
I've tried multiple copies of the same flow (that appears to have run twice, somehow), new flows that are just the location and a compose to grab the body, uninstalling and re-installing the app on an Android (fully up to date) and a Windows Phone (yeah yeah 😉 ...).
To be clear, this is the 'instant' location connector, as pictured below, and the full error is:
"Flow '#ID_NUMBER' cannot be installed."
The Trigger Location is still in preview, so it will have some issues when trigger based on location.
Was the error appears when you try to run it manually, right? If you want to test the trigger, you should take your Phone, open the GPS and Flow, exit the area you circle and then enter it. Please have a try.
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Can you share more details on this one? I tested out on a 200 mtr area radius and it worked as expected. I was unable to manually trigger the flow though but as I stepped out of the configured area the flow worked as expected. Here is a blog I have recently published on geo fence based flows:
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Cheers, @v-litu-msft , aye, thanks for that. I think it's definitely worth ensuring that's known for folks. I had actually taken that into account, but when I'd read the linked post about the issue being resolved, I thought we were high and dry. 😉
Not to worry. 🙂 I think it'd be good to leave this particular thread as unresolved, though, in case others find the same issue and need to raise it. But if you guys have (had to) raise a ticket on your side, do feel free to disassociate or close it out. 🙂
I will keep hoping on this one because it's super cool ... can we bodge something together in PowerApps and bundle it out to our engineers, perhaps?
Morning, @yashag2255 , thanks for your blog link ... that looks lovely, and I've got another tucked away, too. As I'd hoped I'd described, though, this isn't firing on either a modern Samsung Android, and the Lumia whether I'm running it as a test, or on the phone as designed.. I use a 7m radius down one end of the office.
So, not to sound sarcastic (honestly! 🙂 ...) I'm afraid I can't mark "it's working for me" as a fix ... sorry.