I am creating a .NET MAUI Blazor app that makes use of a Razor Class Library (RCL) for shared parts and pages for the Internet, Android and iOS. All the things works as anticipated on Android, Internet and the iOS simulator. Nonetheless, once I get the .ipa file utilizing this line within the terminal
dotnet publish -f:net9.0-ios -c:Launch -r:ios-arm64 /p:ServerAddress=0.0.0.255 /p:ServerUser=Person /p:TcpPort=58181 /p:ArchiveOnBuild=true /p:_DotNetRootRemoteDirectory=/Customers/Person/Library/Caches/Xamarin/XMA/SDKs/dotnet/ /p:EnableAssemblyILStripping=false /p:ServerPassword=Password
and publish the app to TestFlight by way of Transporter, it solely shows the MAUI’s index.html content material (a clean web page / the content material I put in index.html). It additionally reveals Blazor’s An unhandled error has occurred. Reload 🗙, however I wasn’t in a position to get the error message itself (I attempted one way or the other getting it with ErrorBoundary).
I exploit macOS 15.3, XCode 16.2, Visible Studio 17.13, .NET 9. I used to be testing on iOS 18.2 simulator and gadgets that set up my app via TestFlight are utilizing 18.1.1 and 18.3.
I attempted including within the .csproj issues like UseInterpreter=True, MtouchLink (with all potential values) however they didn’t resolve the issue.
I modified the extension of .ipa file to .zip and I see that the .dll of the RCL is current there, so I’ve no clues why it won’t work.
Apparently, if I transfer the web page for route / from the RCL venture to the principle MAUI venture, the web page hundreds accurately in TestFlight. This means a problem with loading pages or parts from the RCL particularly on TestFlight builds.
I additionally tried including a distant logging (if the road of the code runs, I get a log message to my API). And never a single log message I obtained from the parts and pages in RCL. However MAUI half had despatched all the logs proving that it began with no errors.
Any concepts on this?
I had no alternative to examine the app on a bodily iOS machine but, however I’ll strive it quickly and perhaps get extra particulars concerning the error by way of Safari Dev Instruments.