Hello!
I am trying to create a new build of my game, but when I import the new version into unity, I get an error, and the game does not play properly. I am using the same version of unity I used for my first build of the game last year (2019.4.16f1), so I don’t know what is going on!
Attached below are two videos, one of the game working properly in Ready, and the other of the error in unity.
Thanks for your help!
Ok, I tried again using Unity 2019.2.12f1 (I re-exported from Ready), and I get the following error:
NullReferenceException: Object reference not set to an instance of an object
KVirtualJoystick.SetColor (UnityEngine.Color color) (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
K8DirectionMoveBehavior.PropertyUpdated (System.String propertyName) (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
KBehavior.PropertiesUpdated () (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
KBehavior.SetRuntime (System.Boolean running) (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
KObject.SetRuntime (System.Boolean isRunningFlag) (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
KBaseEnviromentManager.Run () (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
KBaseEnviromentManager+d__75.MoveNext () (at <1710231fc3234d4f8df9a2a4a2f22bdc>:0)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at C:/buildslave/unity/build/Runtime/Export/Scripting/Coroutines.cs:17)
Also, the same thing happens as in Video #2 above, where the game is incorrectly displayed, and while the button seams to work, it does not start the game.
@Ready, is there a bug or something here, or is some settings messed up?
Thanks!
Hi @Greenreader9! You need use the “Unity 2019.2.12f1” version for the export now. I can see error with Joystick color, you can try maybe not use the color for the joystick?
If this not help for you, you can send me link of the your project to this topic, i will try check him.
Hi @Ready
I was able to get the scene to open in Unity, however, I now have a different issue.
The control pad for the eagle (Player) does not show fully on the screen in Unity, but does in Ready. My scene is set to “16:9 Portrait (9:16)” in Unity, so I dont know what is happening.
Thanks!
Hi @Greenreader9 ! There is nothing terrible here, it can sometimes happen for the Unity player, try to create a new build for PC or Android, most likely the joystick will fall into place
Thanks for your answer, and now this is getting frustrating. I made a new export from Ready, clicked the “add” button in Unity Hub and added the folder. Selected 2019.2.12f1 and “Android”. Opened the project.
And the error:
The unity icon shows partly green, like its loading
And in Unity, a “Compiling Shader ‘Skybox/Procedural’” blue loading bar
What the going on? And why won’t Unity ever work for me when I’m using Ready projects (besides the very first time)? @Ready@Dravin@Anyone Can you help?
Thanks!
Oh, once before (the day I posted above) I did get it open, and was able to export it. However, Google Play Console gave a multi-line error (I was only able to capture one line)
“Your APK or Android App Bundle needs to have the package name com.COMPANYNAME.TheFlyingEagle.”
Hello,
I watch the video above, and those are the steps I did. I did do it again, and recorded a video. After I got the same error, and realized it was basically a 8 minute video of loading bars, I just screenshotted the main points.
Ok, so I was able to get the project open in Unity (After about 4 failed try’s) after using you instructions above.
When I go to make a update to the app in Google Play, I get this error message. It doesn’t make sense because the package name is “com.GamesByTroy.TheFlyingEagle.apk”
Hi @Greenreader9 ! You made a mistake in the name of the package (In the “Build and Settings” tab), carefully check how you filled in these lines:
In the “Package name” line you must remove all spaces and separate the names with dots, as well as the name of the company and your game must completely match.
@Ready, Wow! I guess this is what happens when you take a game design break for over 3 months
I had changed the name in your “1)” image, but apparently “2)” did not change.
So I export and upload (It works!!!), click “save” and NOOOOOOOOOO, the error!
(I added the “Learn More” link from the screenshot)
I was looking around Google, and found that the “ARM64” box should be checked. So I switched the “Scripting Background” to “IL2CPP” and check all the ARM boxes as well as the x86 box. Exported as an .aab, and the error is still there.
, the “x86” platform has already been removed in the latest versions of Unity and will no longer be used.