iOS Files App Integration Error: SharePoint Uploads Stuck with "01/01/1" Date (Recent Regression)

Question

Hi everyone,

I am experiencing a persistent and frustrating issue when trying to save PDF files directly from a web browser to a SharePoint/OneDrive location using the native iOS "Save to Files" integration.

The Problem:

This feature used to work perfectly fine until just a few weeks ago. Without any changes to my device settings, it has suddenly stopped working. Now, when I try to save a file, it appears in the destination folder within the Files app but never actually uploads. It shows a cloud icon with an exclamation mark, and the file metadata displays a placeholder date of 01/01/1 (a null/Unix zero date).

I am doing a lot of work from my mobile devices and am trying to avoid the "double work" of saving files locally and then manually uploading them via the OneDrive app. I need the direct integration to function as it did previously.

System Info:

• Devices: iPhone and iPad (Both experiencing the same issue).

• OS Version: Both devices are fully up to date.

• App Version: OneDrive and SharePoint apps are fully up to date.

• Context: No setting changes were made; this appears to be a regression caused by a recent iOS or Microsoft app update.

Troubleshooting Already Attempted (I have tried all 12 of these steps with no success):

1. Account Re-authentication: Signed out and back into the OneDrive/SharePoint apps.
2. Connection Check: Switched between WiFi and Cellular; disabled all VPNs.
3. File Naming: Renamed PDFs to simple names (e.g., test.pdf) to rule out special characters.
4. App Offloading: Offloaded the OneDrive app via iOS Settings to refresh system files.
5. File Provider Toggle: Toggled the OneDrive/SharePoint provider OFF and ON within the Files app "Browse" menu.
6. Background App Refresh: Confirmed it is ON for both Files and OneDrive apps.
7. Upload Queue Clearance: Manually checked and cleared the "Uploads" section within the OneDrive app.
8. SharePoint Shortcut Method: Used "Add Shortcut to My Files" in OneDrive to simplify the SharePoint path.
9. Compliance Check: Verified no "MAM" or "Intune" blocks in Microsoft Authenticator/Company Portal.
10. The "Nuclear" Reset: Deleted apps, Force Restarted the device, reinstalled, and toggled "Reset App" in Settings.
11. Direct Share Sheet Bypass: Tried "Open in OneDrive" (the app icon) instead of "Save to Files" (the folder icon).
12. Automation/Shortcuts: Attempted to use the iOS "Shortcuts" app to automate the upload directly to the path.

Despite these 12 steps, the "File Provider" extension continues to fail. Given that this worked a few weeks ago, it feels like a bug in the recent versioning. Has anyone else encountered this sudden "01/01/1" error?

Answer 1

Dear @Michaël Slagter, 

Good day, and I appreciate the clear explanation of your concern.   

I have come across reports from other community users describing similar behavior, and I truly appreciate the time and effort you’ve already invested in troubleshooting this issue on your own. You’ve completed all the appropriate end‑user troubleshooting steps, which is very helpful.

At this time, I’ve reviewed the advisories and incidents listed in the Microsoft 365 admin center and didn't find any related notifications. However, this doesn't necessarily mean the issue does not exist, as it may currently affect only a small number of users and hasn't yet been widely reported to administrators.

• As the next best step, I strongly recommend contacting your IT administrator to submit a support ticket through the Microsoft 365 Admin Center > Support > Help & Support for further investigation. In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support 

A Microsoft technical support engineer can conduct a remote session to review the issue in detail, validate backend configurations, and run any required synchronization or diagnostic tools. If necessary, the case can be escalated to a specialized team for more in‑depth analysis and resolution. 

I would like to clarify that my role is limited to sharing public documentation, testing observations and general troubleshooting guidance. I don't have access to internal diagnostic tools, engineering backlogs, or build level investigations. Because of that, I am not able to confirm whether this behavior is linked to a known product issue or bug.   

Also, as many members of the community may not yet be aware of this behavior. Sharing or highlighting this response can help bring greater visibility to the issue, making it easier for others who are experiencing similar challenges to find relevant information and support.    

I hope this helps clarify the current situation and the available next steps. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.     

Thank you for your patience and understanding.  

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".             

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Answer 2

I am having the same exact issue and have been going crazy for the past two days. I have gone through all of the resets that you mentioned in your message. I’ve even called my IT company who are at a loss and did not even know that others were experiencing the same issue. If anybody knows what is going on or how to fix it, please, would love to know.