Should force write the file by setting it to writeable first
On my own repo I made the following change in Assets/MaxSdk/Scripts/IntegrationManager/Editor/AppLovinInternalSettings.cs to Save()
Note that due to how the other settings file Assets/MaxSdk/Resources/AppLovinSettings.asset is managed, it does not have this same issue (Unity forces it to writeable I believe).
Alternatively, there is an argument to be made that applovin should respect the user's read-only flag. As a user I disagree, but if you take this position then the correct fix is to show an explicit error to the user telling them that their settings failed to save, and that they should ensure the file is writeable.
How to Reproduce
Have the internal settings file, ProjectSettings/AppLovinInternalSettings.json set to read-only, as is common in some version control systems like perforce
Change an internal setting, in the IntegrationManager, i.e. toggle the checkbox for "Localize User Tracking Usage Description"
MAX Plugin Version
6.0.1
Unity Version
2021.3.11f1
Device/Platform Info
Unity Editor
Current Behavior
Fails to write settings if they are read-only
Expected Behavior
Should force write the file by setting it to writeable first
On my own repo I made the following change in
Assets/MaxSdk/Scripts/IntegrationManager/Editor/AppLovinInternalSettings.cstoSave()Note that due to how the other settings file
Assets/MaxSdk/Resources/AppLovinSettings.assetis managed, it does not have this same issue (Unity forces it to writeable I believe).Alternatively, there is an argument to be made that applovin should respect the user's read-only flag. As a user I disagree, but if you take this position then the correct fix is to show an explicit error to the user telling them that their settings failed to save, and that they should ensure the file is writeable.
How to Reproduce
ProjectSettings/AppLovinInternalSettings.jsonset to read-only, as is common in some version control systems like perforceAdditional Info
No response