Hi @Ulvi Yurtsever
This is a very useful reproduction, especially because editing an already-synced file immediately releases the queued new-file upload.
Based on the behavior you described, I would not focus on file type, filename, extended attributes, or the individual OneDrive folder anymore. You have already isolated most of those variables.
The pattern looks more like the OneDrive/File Provider sync pipeline is entering an idle state and failing to wake correctly when the next event is a newly created file. Modifying an existing synced file appears to generate a different change notification that wakes the sync engine and causes the pending upload queue to resume.
Since you are specifically using the Mac App Store version, I would run one additional A/B test:
- Confirm your current OneDrive version.
Quit OneDrive.
Run the appropriate OneDrive reset command from the current app bundle.
Remove the App Store build.
Install the latest standalone OneDrive for Mac build directly from Microsoft.
Configure the same personal account.
Repeat your exact test:
modify an existing file
create a small new file and confirm it uploads
leave OneDrive idle for 20–25 minutes
create another new file
Microsoft maintains separate App Store and standalone versions of OneDrive on macOS, and they should not be installed/configured for the same account at the same time.
If the standalone build does not reproduce the issue, that would strongly suggest something specific to the App Store build or its interaction with macOS File Provider.
If the same behavior occurs with both builds, I would consider this a strong candidate for a OneDrive/macOS File Provider bug rather than a local file problem.
I would also capture these details before opening a support case:
OneDrive version/build number
macOS version
exact idle interval before reproduction
timestamps for the new-file creation and existing-file modification
whether fileproviderd shows increased activity when the existing file is modified
whether the pending file appears immediately in OneDrive Sync Activity
Your reproduction is consistent enough that I would report it to Microsoft rather than continue resetting the client. Microsoft’s current macOS release notes include ongoing reliability fixes, but I could not find a documented known issue matching this exact idle/new-file pattern.
If this answer was helpful, please consider marking it as helpful or accepting it as the answer. It may also help other Mac users reproduce the same sync issue.Hi Ulvi,
This is a very useful reproduction, especially because editing an already-synced file immediately releases the queued new-file upload.
Based on the behavior you described, I would not focus on file type, filename, extended attributes, or the individual OneDrive folder anymore. You have already isolated most of those variables.
The pattern looks more like the OneDrive/File Provider sync pipeline is entering an idle state and failing to wake correctly when the next event is a newly created file. Modifying an existing synced file appears to generate a different change notification that wakes the sync engine and causes the pending upload queue to resume.
Since you are specifically using the Mac App Store version, I would run one additional A/B test:
Confirm your current OneDrive version.
Quit OneDrive.
Run the appropriate OneDrive reset command from the current app bundle.
Remove the App Store build.
Install the latest standalone OneDrive for Mac build directly from Microsoft.
Configure the same personal account.
Repeat your exact test:
modify an existing file
create a small new file and confirm it uploads
leave OneDrive idle for 20–25 minutes
create another new file
Microsoft maintains separate App Store and standalone versions of OneDrive on macOS, and they should not be installed/configured for the same account at the same time.
If the standalone build does not reproduce the issue, that would strongly suggest something specific to the App Store build or its interaction with macOS File Provider.
If the same behavior occurs with both builds, I would consider this a strong candidate for a OneDrive/macOS File Provider bug rather than a local file problem.
I would also capture these details before opening a support case:
OneDrive version/build number
macOS version
exact idle interval before reproduction
timestamps for the new-file creation and existing-file modification
whether fileproviderd shows increased activity when the existing file is modified
whether the pending file appears immediately in OneDrive Sync Activity
Your reproduction is consistent enough that I would report it to Microsoft rather than continue resetting the client. Microsoft’s current macOS release notes include ongoing reliability fixes, but I could not find a documented known issue matching this exact idle/new-file pattern.
If this answer was helpful, please consider marking it as helpful or accepting it as the answer. It may also help other Mac users reproduce the same sync issue.