Share via

Deep Linking Issue with Edge Browser in iOS App – Opening Appstore Instead of App

Anonymous
2024-01-04T07:54:14+00:00

I am currently facing an issue with deep linking in my iOS application when Microsoft Edge is set as the default browser on the device. In our app, users receive invitations via email, and when they press the accept or decline button, the iOS app opens, triggering a dedicated API call based on the URL received in the userActivity method within the AppDelegate.

The current behavior is as follows:

When Safari is the default browser, the process works seamlessly, and the app opens directly.

However, when Microsoft Edge is set as the default browser, it opens the App Store link in a popover, with an option to open the app if installed.

I would like to achieve the same behavior with Microsoft Edge as with Safari, where the app opens directly rather than redirecting to the App Store.

Here is an example of the deep link URL format I am using: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2F

Is there a specific configuration or workaround to ensure that Microsoft Edge, when set as the default browser, opens the app directly instead of redirecting to the App Store?

Any insights or suggestions would be greatly appreciated.

I am expecting that this safe link works the same as works with a safari in iOS Devices.

Microsoft Edge | Open the browser | iOS

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-06T13:52:52+00:00

    Hi

    Thanks for your reply.

    From your description, the issues on Deep Linking Issue with Edge Browser in iOS App – Opening Appstore Instead of App is out of reach of the response support community. It is more suitable for publishing on Microsoft Learn, you can click on "Ask a question", there are experts who can provide more professional solutions in that place.

    Here is a link to the forum where you can raise specific scenarios and share your idea to help solve the problem.

    I won't be able to help you, but I'll leave that question open in case one of our amazing volunteers has ideas for you.

    Best regards

    Derrick Qian | Microsoft Community Support Specialist

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2024-01-05T09:12:52+00:00

    Hi

    Welcome to Microsoft community.

    Handling deep linking in iOS can be tricky, especially when dealing with different browsers that may not handle URLs in the same way as Safari does. The issue you're encountering with Microsoft Edge might be due to how Edge handles redirections to deep links. Here are some suggestions and considerations that may help you resolve the issue:

    1. Universal Links: Ensure that you are using Universal Links and that they are correctly set up. Universal Links are the recommended way by Apple to handle deep linking because they allow for a seamless transition between a web domain and the corresponding content within an app.
    2. App Association File (AASA): Check your apple-app-site-association file on your server to make sure it’s correctly configured and accessible over HTTPS without any redirects. The AASA file should be properly associated with your app and should include the paths that should open your app.
    3. Edge Handling of Universal Links: While Safari has built-in support for Universal Links, third-party browsers like Edge may handle these links differently. Microsoft Edge might not fully support the same deep linking behavior as Safari.
    4. Fallback Mechanism: It's common to implement a fallback mechanism for cases where the app is not installed. However, if the app is installed, the browser should open the app directly. Make sure the logic in your website's redirection script correctly detects the installed app and redirects accordingly.
    5. Test Other Browsers: Check the behavior with other third-party browsers like Chrome or Firefox to see if they exhibit the same issue. This can help you determine if the problem is specific to Edge or if it's a broader issue with how non-Safari browsers handle deep links on iOS.
    6. URL Format: Sometimes, the issue could be with the URL format or encoding. Try simplifying the URL to the basic format required by your app and test if Edge handles it differently.
    7. Community and Forums: Engage with developer communities such as Stack Overflow or the Apple Developer Forums. Other developers might have encountered similar issues and could have workarounds or solutions.
    8. Documentation Review: Review Microsoft Edge's and iOS's documentation for any updates or changes in how they handle deep linking.

    Unfortunately, without control over how third-party browsers handle deep links, there might be limitations to what you can achieve. However, starting with these steps can help you troubleshoot the issue and possibly find a workaround.

    Best regards

    Derrick Qian | Microsoft Community Support Specialist

    9 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-05T14:13:26+00:00

    Hi Derrick19 - MSFT

    As I go through your all points and issues we are currently experiencing with the SafeLink policy.
    Our organization utilizes the SafeLink policy, and we have observed that the deep link functions seamlessly across browsers when SafeLink is not applied. However, upon adding SafeLink to the URL, the deep link functionality is restricted to Safari only.

    I have provided both the SafeLink and non-SafeLink URLs for your reference:

    SafeLink URL:
    [https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2F<SITELINK (Eg.xxx.yyy.com)>.%2FteamDay%3FteamDayId%3DHTWmmt7cmYyd7LawwhMq5%2BMyNt%2Bf8eUCz25pzmsTUMo%3D%26domainUrl%3Dhttps%3A%2F%2Fxxx.dev.com&data=05%7C02%7C<username>%40<company domain>%7Cb6ffab414d034bbceb0108dbfd382f0c%7C454af8f364734bce8aa5f9403e1d1271%7C0%7C0%7C638382189984623308%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=B5rzVQ0alWjIsT7ycI2oZrNjeVPM%2BeoMk0YDpMZk6q4%3D&reserved=0]

    Non-SafeLink URL:
    [https://xxx.yyysoftware.com/teamDay?teamDayId=p0RQIAsd4vaTk1yHGuTUdBCDmP0ZK1CuR8Q3JfSPJvU=&domainUrl=https://xxx.dev.com]

    Any insights or suggestions would be greatly appreciated.

    5 people found this answer helpful.
    0 comments