Bug 55962 - Pdf with accent in file name won't open
Summary: Pdf with accent in file name won't open
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 10.8 (d15-1)
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-05-04 14:00 UTC by Alexandre Pepin
Modified: 2017-06-16 13:27 UTC (History)
4 users (show)

Tags: 15.1I
Is this bug a regression?: ---
Last known good build:

Sample project (30.21 KB, application/zip)
2017-05-04 14:00 UTC, Alexandre Pepin

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 55962 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Alexandre Pepin 2017-05-04 14:00:21 UTC
I just upgraded from Xamarin to Xamarin and my Pdf with an accent in the file name won't open anymore when using UIDocumentInteractionController. The problem only occurs on my iPad and not on the simulator.

# Steps to reproduce
Run the attached project.

# Expected behavior
To open the Pdf

# Actual behavior
It shows a grey screen instead of the Pdf

# Supplemental info (logs, images, videos)
If you change the documentToOpen to "documentPdfWithoutAcuteAccent" it works. But removing the accent is not a solution. In my real use case, the Pdf are downloaded from the user's Dropbox so I have no control over the name.

I also added some tests in the attached solution: 
"File.Exists(documentPdfWithAcuteAccent)" and "File.Exists(documentPdfWithoutAcuteAccent)" both return true, but "fileManager.FileExists(documentPdfWithAcuteAccent)" returns false and "fileManager.FileExists(documentPdfWithoutAcuteAccent)" returns true.
I think it is a problem with NSUrl or NSFileManager because it can't find my Pdf file with an acute accent. Or there is something not consistent between .Net and iOS

# Test environment (full version information)
I tested on an iPad model MD788CL/B running iOS 10.3.1

My full Visual Studio Version information:
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01055

Installed Version: Professional

Visual Basic 2015   00322-40000-00000-AA258
Microsoft Visual Basic 2015

Visual C# 2015   00322-40000-00000-AA258
Microsoft Visual C# 2015

Visual C++ 2015   00322-40000-00000-AA258
Microsoft Visual C++ 2015

Windows Phone SDK 8.0 - ENU   00322-40000-00000-AA258
Windows Phone SDK 8.0 - ENU

Application Insights Tools for Visual Studio Package   7.18.00214.2
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2015.1   14.1.20810.0
ASP.NET and Web Tools 2015.1

ASP.NET Web Frameworks and Tools 2012.2   4.1.41102.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

ASP.NET Web Frameworks and Tools 2013   5.2.40314.0
For additional information, visit http://www.asp.net/

Azure App Service Tools v2.8.1   14.0.11123.0
Azure App Service Tools v2.8.1

Common Azure Tools   1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

JavaScript Language Service   2.0
JavaScript Language Service

JavaScript Project System   2.0
JavaScript Project System

JustDecompile Tools   1.0
Makes JustDecompile functionality available in VIsual Studio. Requires JustDecompile installation.

Merq   1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.

Microsoft .NET Core Tools (Preview 2)   14.1.20810.0
Microsoft .NET Core Tools (Preview 2)

Microsoft Azure Mobile Services Tools   1.4
Microsoft Azure Mobile Services Tools

Mono Debugging for Visual Studio   Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.

NuGet Package Manager   3.5.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

PoxAutoRun   1.0
PoxAutoRun Visual Studio Package Detailed Info

PreEmptive Analytics Visualizer   1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

SQL Server Data Tools   14.0.60519.0
Microsoft SQL Server Data Tools

tangible T4 Editor   2.3.0
tangible engineering GmbH

TypeScript tools for Visual Studio

Web Compiler   1.11.326
Compiler for LESS, Sass and CoffeeScript files

Web Essentials 2015.3   3.0.235
Adds many useful features to Visual Studio for web developers. Requires Visual Studio 2015

Xamarin (3f99c5a)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android (b16fb82)
Visual Studio extension to enable development for Xamarin.Android.

Xamarin.iOS (7656cc6)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 1 Alexandre Pepin 2017-05-04 14:00:48 UTC
Created attachment 21946 [details]
Sample project
Comment 2 Sebastien Pouliot 2017-05-04 15:18:01 UTC
This is due to the new file system (APFS) that Apple introduced in iOS 10.3. Sadly Apple did a bad job at explaining the impact of the new file system.

More details in https://mjtsai.com/blog/2017/03/24/apfss-bag-of-bytes-filenames/
Comment 3 Alexandre Pepin 2017-05-04 17:59:37 UTC
Is there a workaround to this problem?