Search Issue Tracker
Fixed in 1.0.0-preview.8
Votes
3
Found in [Package]
1.0.0
Issue ID
1103909
Regression
No
Error of InvalidOperationException appears when Mobile Notifications package is being installed
To reproduce:
1. Create a new project
2. Go to Package manager
3. Install Mobile Notifications package
Actual result: There is an error
Expected result: There should be no errors
Reproduced on: 2018.2.0a1; 2018.2.18f1; 2018.3.0a1; 2018.3.0b12; 2019.1.0a1; 2019.1.0a10
Error:
InvalidOperationException: Stack empty.System.Collections.Generic.Stack`1[T].ThrowForEmptyStack () (at <42a03650bc6049e481a9b961c8331371>:0)System.Collections.Generic.Stack`1[T].Pop () (at <42a03650bc6049e481a9b961c8331371>:0)
On 2018.2.18f1 getting errors: Platform name 'Lumin' not supported.
Assembly has reference to non-existent assembly 'Unity.Notifications.Android' (Packages/com.unity.mobile.notifications/Editor/Unity.Mobile.Notifications.Editor.asmdef)
On 2018.2.0a1: Platform name 'Lumin' not supported.
Supported platform names:
"Android",
"Editor",
"iOS",
"LinuxStandalone32",
"LinuxStandalone64",
"LinuxStandaloneUniversal",
"macOSStandalone",
"Nintendo3DS",
"PS4",
"PSVita",
"Switch",
"tvOS",
"WebGL",
"WindowsStandalone32",
"WindowsStandalone64",
"WSA",
"XboxOne"
(Packages/com.unity.mobile.notifications/Runtime/iOS/Unity.Notifications.iOS.asmdef)
-
TalespinMick
Dec 18, 2018 09:43
I can confirm the platform not supported error is fixed, but there are now two warnings:
"C:/Users/Mick/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.mobile.notifications@1.0.0-preview.8/Runtime/Android/AndroidNotificationCenter.cs(482,20): error CS0414: Warning as Error: The private field `Unity.Notifications.Android.AndroidNotificationCenter.AndroidSDK' is assigned but its value is never used"
"C:/Users/Mick/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.mobile.notifications@1.0.0-preview.8/Runtime/iOS/iOSNotificationCenter.cs(663,60): error CS0067: Warning as Error: The event `Unity.Notifications.iOS.AuthorizationRequest.OnAuthRequest' is never used"
Just to let you guys know :)
-
TalespinMick
Dec 18, 2018 09:12
Wow thank you @_Paulius! Appreciate the swift response.
-
_Paulius
Dec 17, 2018 18:41
I've changed the milestone to 2018.2 and made a package version with a fix.
-
_Paulius
Dec 17, 2018 18:41
This is resolved in `com.unity.mobile.notifications : 1.0.0-preview.8`, it's not in production repository yet (should be promoted in a day or two). Currently it's possible to get this from the staging repo by manually adding this to the project's Packages/manifest.json file:
{
{
//all other packages
"com.unity.mobile.notifications": "1.0.0-preview.8"
},
"registry": "https://staging-packages.unity.com"
} -
TalespinMick
Dec 17, 2018 17:18
This "Fixed" state is very infuriating, the package is available in 2018.2 but is only "fixed" in 2018.3?
We are deep into our project and need to use the notifications package in 2018.2 since we can't upgrade to 2018.3... -
ZanLeO
Dec 09, 2018 23:22
on 2018.2.19f1 too
-
siempus
Dec 02, 2018 05:26
I confirm this issue on 2018.2.17f1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.0.0-preview.8):
Fixed in com.unity.mobile.notifications : 1.0.0-preview.8