Search Issue Tracker
Fixed
Fixed in 2.3.1
Votes
1
Found in [Package]
2.3.0
Issue ID
MNB-70
Regression
Yes
[UWP] Universal Windows Platform build fails when Mobile Notifications package v2.3.0 is installed
Reproduction steps:
1. Open the attached project “UWPProject”
2. Ensure Mobile Notification v2.3.0 is installed
3. Build the project for Universal Windows Platform
4. Observe the build process
Expected result: The build is completed successfully
Actual result: Build failed with the error “mobilenotifications.androidlib is a directory, which is not supported”
Reproducible with: 2.3.0(2021.3.33f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a18)
Not reproducible with: 2.2.0, 2.2.1, 2.2.2 (2021.3.33f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a18)
Testing environment: Windows 10 Pro 22H2
Full error:
Building C:\Projects\FreshProject\Unity2022\Deploy\UWP\Unity2022\Plugins\mobilenotifications.androidlib failed with output:
The source path Library\PackageCache\com.unity.mobile.notifications@2.3.0\Runtime\Android\Plugins\mobilenotifications.androidlib is a directory, which is not supported.
UnityEditor.BuildPipeline:BuildPlayer (UnityEditor.BuildPlayerOptions)
BuildScript:BuildForPlatform (UnityEditor.BuildTarget,string[],string,string) (at Assets/Scripts/Editor/BuildScript.cs:42)
BuildScript:Build () (at Assets/Scripts/Editor/BuildScript.cs:18)
Notes: Building works fine for other platforms, Android, Standalone (macOS and Windows)
Comments (1)
-
FixItFelix
Dec 08, 2023 13:47
We just had the same experience. We had to downgrade to version 2.2.2. to make it work again.
I think the mobile notifications package has some restructuring. The "mobilenotifications" folder is now recognized as a plugin but the platform is set to any instead of Android. Before it had 4 different plugins set to Android only.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2.3.1):
This is already fixed in master.