SharePoint / SharePoint/sp-dev-docs

SPFx in Outlook Mobile for iOS doesn't load

Open
#10,073 4 comments 0 reactions 1 assignee View on GitHub

@Amey-MSFT is already working on this.

Since Mar 24, 2025.

area:spfx sharepoint-developer-support type:bug-confirmed
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details

iPhone 12 Pro running iOS 18.2.1
spfx version 1.19
Outlook v. 4.2452.0 (though it hasn't work for many months, if ever)

Describe the bug / error

I can deploy my spfx webpart to Teams and Outlook and it works almost everywhere like Outlook on web, Outlook for Windows and in Teams (in iOS, desktop and web) but just doesn't want to play ball on the iOS app
I just get a perpetual loading icon and it never gets any further

Image

It is possibly related to a previous issue I raised with safari (though that has workarounds)
https://github.com/SharePoint/sp-dev-docs/issues/9795

Steps to reproduce
  1. Create a new webpart using yeoman with React as the framework
  2. Deploy the app to your sharepoint tenant
  3. Add the app to Teams (also via sharepoint)
  4. Make sure the app is accessible to your user in the teams admin portal
  5. The add-in/app should also appear in admin.microsoft.com under integrated apps, if necessary assign your user to it
  6. Open the webpart in outlook for mobile (iOS)

Note: it can take a few hours before the add-in/app appears in Outlook

Expected behavior

I'd expect the webpart to load

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.