You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create project (MS.iOS, MS.Maui) with app icon set. Build from symlink location like /var (/private/var) - default location for Jenkins on Mac OS (JENKINS_HOME=/var/lib/jenkins or JENKINS_HOME=/var/jenkins_home).
Archive for Publishing (IPA) or build with BuildIpa set to true.
Then it tries to feed OutputPaths with these paths that seems to be treated as a location outside app bundle - as it is not directly from the underlaying bundle but many levels up the file tree:
…h for the LogicalName property. Fixesxamarin#20330.
This fixes an issue where we'd compute a LogicalName property that was outside
of the app bundle, resulting in broken resources in the app bundle (in
particular the app icon would be missing).
So instead of something like this:
LogicalName: ../../../../../../../../../tmp/testapp/obj/Debug/net8.0-ios/iossimulator-arm64/actool/bundle/Assets.car
we'll now get:
LogicalName: Assets.car
and the icons will be correctly embedded in the app bundle.
Fixesxamarin#20330.
Steps to Reproduce
/var
(/private/var
) - default location for Jenkins on Mac OS (JENKINS_HOME=/var/lib/jenkins
orJENKINS_HOME=/var/jenkins_home
).BuildIpa
set to true.Expected Behavior
App is using icon that was specified in the project.
Actual Behavior
Default app icon is being used.
Environment
Version information
Build Logs
Diagnostic build (xcrun with actool arg):
It mixes '/private/var/...' with '/var/..' for
output-files
entries.It tries to resolve relative
LogicalName
paths but fails somehow on the symlink (/var
) and creates some awkward looking entry:Then it tries to feed OutputPaths with these paths that seems to be treated as a location outside app bundle - as it is not directly from the underlaying bundle but many levels up the file tree:
It seems that resolve algorithm does not play well with symlinks and for some reason is going further in the tree level trying to unwind the link.
In working build (no symlink involved) bundle resources are referenced directly from the App.app:
Related to:
The text was updated successfully, but these errors were encountered: