Strange console output when starting app: "Forcing GfxDevice: Null" - unity3d

My Unity app is successfully built, but it's not working.
I always see the strange console output below after the app starts.
What's going wrong?
Mono path[0] - 'E:/Mvp/New Unity Project (6)_Data/Managed'
Mono config path - 'E:/Mvp/MonoBleedingEdge/etc'
Initialize engine version: 2019.2.15f1 (dcb72c2e9334)
[XR] Discovering subsystems at path E:/Mvp/New Unity Project (6)_Data/UnitySubsystems
Forcing GfxDevice: Null
GfxDevice: creating device client; threaded=0
NullGfxDevice:
Version: NULL 1.0 [1.0]
Renderer: Null Device
Vendor: Unity Technologies
Begin MonoManager ReloadAssembly
- Completed reload, in 0.059 seconds
UnloadTime: 0.415900 ms


Seems like server build.
In your build setting menu, do you have the "Server Build" checkbox checked?
If yes, un-check that and retry.


This could be a symptom of the same problem described here:
"Shader Unsupported" when starting Unity server with -batchmode -nographics flags
For Unity 2021: make sure you dont have Dedicated Server selected in the Build Settings. This can also happen when you simply take a look at the Dedicated Server Settings tab in the Player settings.

Related

Visual Studio Community 2022 Android Emulator won't build

I’ve tried almost everything I can think of and none of it has even made a dent.
Whenever I try to execute my application, the device attempts to boot twice, quickly flashing on screen then disappearing, with a warning message inside the temporarily emulated device reading: “Resetting for cold boot: emulator engine failed” (I have tried this from both new devices and devices with force.ColdBoot disabled).
Whenever I try to execute my application, the device attempts to boot twice, quickly flashing on screen then disappearing, with a warning message inside the temporarily emulated device reading: “Resetting for cold boot: emulator engine failed” (I have tried this from both new devices and devices with force.ColdBoot disabled).
Nothing seems out of place in the Android Debug Properties menu.
I have HAXM enabled.
I’ve reinstalled Visual Studio. The emulated devices were still in Android Device Manager in the new version if that matter.
Every thread I’ve searched is either irrelevant, outdated, or merely tangential to my problem.
It changes a bit with each of the modifications I made, but the output from the build is always something like this:
Build started...
Starting emulator tablet_h-dpi_13_5in_-_api_33 ...
1>------ Build started: Project: MobileApplicationAssessment.Android, Configuration: Debug Any CPU ------
C:\Program Files (x86)\Android\android-sdk\emulator\emulator.EXE -netfast -accel on -avd tablet_h-dpi_13_5in_-_api_33 -prop monodroid.avdname=tablet_h-dpi_13_5in_-_api_33
1>C:\Users\Alistair\source\repos\MobileApplicationAssessment\MobileApplicationAssessment.Android\Properties\AndroidManifest.xml : warning XA4211: AndroidManifest.xml //uses-sdk/#android:targetSdkVersion '31' is less than $(TargetFrameworkVersion) ''. Using API-33 for ACW compilation.
1>C:\Users\Alistair\source\repos\MobileApplicationAssessment\MobileApplicationAssessment\MobileApplicationAssessment.csproj : warning NU1701: Package 'Microsoft.Bcl 1.1.6' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.
1>C:\Users\Alistair\source\repos\MobileApplicationAssessment\MobileApplicationAssessment\MobileApplicationAssessment.csproj : warning NU1701: Package 'Microsoft.Bcl.Async 1.0.165' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.
1>C:\Users\Alistair\source\repos\MobileApplicationAssessment\MobileApplicationAssessment\MobileApplicationAssessment.csproj : warning NU1701: Package 'PCLStorage 1.0.2' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.
1> MobileApplicationAssessment.Android -> C:\Users\Alistair\source\repos\MobileApplicationAssessment\MobileApplicationAssessment.Android\bin\Debug\MobileApplicationAssessment.Android.dll
2>Starting deployment to tablet_h-dpi_13_5in_-_api_33 ...
2>Starting emulator tablet_h-dpi_13_5in_-_api_33 ...
2>C:\Program Files (x86)\Android\android-sdk\emulator\emulator.EXE -netfast -accel on -avd tablet_h-dpi_13_5in_-_api_33 -prop monodroid.avdname=tablet_h-dpi_13_5in_-_api_33
2>Emulator tablet_h-dpi_13_5in_-_api_33 cannot be started.
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Elapsed 00:31.315 ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
========== Elapsed 00:31.315 ==========
Any help would be greatly appreciated, and it’s worth noting I’ve only been using VS for about a year, so I might not know all the terminology and whatnot, so if you could break down those in your answers that would, also, be appreciated.

Unity Advertisment with Meditation not Showing Test Ads

I just upgrade advertisement package to Advertisement with Meditation package. I used sample project scripts. In unity editor everything is OK but when i build on physical android test device i'm getting this log:
"Initialization Failed: Unknown:Some services couldn't be initialized. Look at inner exceptions to get more information."
and test ads are not showing on android device.
I couldn't figure out what it means. I did a google search but couldn't find any results.
I've already enabled test mode in editor: Services->Ads->Test mode enable
My unity version: 2019.4.16f1
Adversitement with Meditation verison:
1.0.4

Issue in setting up the Android emulator with React native

I am fairly new to React native and trying to set up Android environment with Visual studio. All the installation has been fairly successful, however, when I try to run the sample app on the android emulator executing the npx react-native run-android command it shows below error -
'C:\Users\Home' is not recognized as an internal or external command,
operable program or batch file.
error Failed to launch emulator. Reason: Could not start emulator within 30 seconds..
Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details
java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
at org.codehaus.groovy.vmplugin.VMPluginFactory.<clinit>(VMPluginFactory.java:43)
at org.codehaus.groovy.reflection.GroovyClassValueFactory.<clinit>(GroovyClassValueFactory.java:35)
at org.codehaus.groovy.reflection.ClassInfo.<clinit>(ClassInfo.java:109)
However, when i execute adb devices on visual studio, it shows the list of emulator connected -
List of devices attached
emulator-5554 device
What could be the possible reason? Is this because my users name is Home PC? (Is this because there is a space in between) and it is not able to get the correct path?

This is because your java version is updated to the latest version and gradle is not supported with the installed version. what you can do is update the gradle as well
So go to gradle/wrapper folder inside the android folder
Edit gradle-wrapper.properties file and replace distributionUrl
with following value
https\://services.gradle.org/distributions/gradle-6.3-all.zip
distributionUrl=https\://services.gradle.org/distributions/gradle-6.3-all.zip

I too faced the same issue.The problem is with the JDK. From JDK 14 i downgraded to JDK 11(LTS) version. And it worked.
Hope it helps.

Install Java 8 version, which is available Java 8 download
Gradle is not keeping up with the Java Latest versions, so roll back
to previous versions

Xamarin.iOS: Deploying to device fails with "failed to acquire command execution log"

My iOS app built in Visual Studio with a Xamarin Mac build host runs on the iOS simulator but does not deploy to the device. The Mac server log shows this:
[2013-07-30 13:28:45.7] Handling with command: [Build: CommmandUrl=Build] (20)
[2013-07-30 13:28:45.7] Attempting to acquire command execution lock, timeout set to 00:10:00
[2013-07-30 13:30:56.4] Error: Failed to acquire command execution log, the request timed out
[2013-07-30 13:30:56.4] Command [Build: CommmandUrl=Build] finished (17)
Incidentally, is that a typo in line 3 - shouldn't it read "lock" not "log"?
We are using Xamarin Studio 4.0.10 (build 7), Xamarin.iOS 6.4.0.2 (Business Edition), XCode 4.6.2 (2067.2) Build 4H1003.
What is the cause of this error, and how can we get past it?

After talking with Xamarin folks I was told that a fix was included in the Beta for Xamarin.iOS 6.4.1. I switched my Xamarin Studio to the Beta Channel (via the update dialog) and am now able to deploy as before.

BlackBerry Android Runtime ADB failed

I try to Packaging project with Android Runtime For BlackBerry I done every thing
-Simulator, ADT- for eclipse .. when i test the app i got this error :
[2013-04-13 13:16:04 - BlackBerryTest] Packaging project BlackBerryTest
[2013-04-13 13:16:11 - BlackBerryTest] Launching BlackBerry Android Runtime...
[2013-04-13 13:16:20 - BlackBerryTest] Connecting to ADB...
[2013-04-13 13:17:23 - BlackBerryTest] Status ERROR: net.rim.ajde code=4 Connecting 192.168.72.128 to ADB failed! null children=[Status ERROR: net.rim.ajde code=0 Please check if the Android player was fully started when you got this error. If not, you can either increase the Android player launch timeout on the BlackBerry->BlackBerry Android Development Tools preference page or wait until the Android player is fully started and try again. null]
in the Simulator there is splash screen contain blackberry 10 logo start about 2 sec and then close and eclipse still Connecting to ADB... about a minute then I got error to connect.
**
UPDATE :
**
Now I got this message
04-25 12:01:15.539: I/navigatorshell(17789061): no app URI, just launch AP and exit
Any Idea ?

This is usually caused by the Android Runtime taking a very long time to load, and in some cases, never actually loading.
The root cause is that the simulator is running very slowly. If you haven't already, enable virtualisation in your BIOS, this makes a massive difference to simulator performance and solved this issue for me.
There's a video about this here: http://devblog.blackberry.com/2012/08/performance-increase-blackberry-10-simulator/