-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saving Prefab to immutable folder is not allowed. #3593
Comments
This guy has the same problem as me.#3350 |
These prefabs are for demonstration and are not intended for modification. That said, I will look into a fix for the issue. |
i'm having the same issue with almost identical setup on windows
|
This asset is randomly changed after pressing play: Line 36-38, before changes:
After changes:
@NVentimiglia
if it's doing that, please change the code to
|
Hi, Did anyone found the Solution to this problem. I am facing the same issue. I have installed admob sdk using openupm and it is giving error while making build. |
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
`using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using GoogleMobileAds.Api;
public class test : MonoBehaviour
{
// These ad units are configured to always serve test ads.
#if UNITY_ANDROID
private string _adUnitId = "ca-app-pub-3940256099942544/6300978111";
#elif UNITY_IPHONE
private string _adUnitId = "ca-app-pub-3940256099942544/2934735716";
#else
private string _adUnitId = "unused";
#endif
}
`
2.When running a scene, choose to mount this scripted game object.
3.Cancel the run, change the active of this gameobject in inspector to false and then to true, save the scene
4.The following error will be generated
Saving Prefab to immutable folder is not allowed: Packages/com.google.ads.mobile/GoogleMobileAds/Editor/Resources/PlaceholderAds/Banners/BANNER.prefab UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()
Here are the source files
归档.zip
The text was updated successfully, but these errors were encountered: