Develop Reference

React Native App crashing on release mode but working fine debug mode

My React native app was working fine few days back on both release and debug mode but from yesterday it keeps crashing on start in release mode, but it is working perfectly fine on debug mode.
When i ran
adb logcat *:E
it gave me following logs but i can't find anything on internet related to this
02-17 18:30:56.108 564 595 E libPowerHal: Could not open '/proc/1705/comm'
02-17 18:30:56.108 564 595 E libPowerHal: error : 13, Permission denied
02-17 18:30:56.260 22398 22398 E com.blackhedge: Not starting debugger since process cannot load the jdwp agent.
02-17 18:30:56.282 564 595 E libPowerHal: perfLockRel handle:293
02-17 18:30:56.517 22398 22398 E libc : Access denied finding property "ro.vendor.df.effect.conflict"
02-17 18:30:56.518 534 22445 E ResolverController: No valid NAT64 prefix (105, <unspecified>/0)
02-17 18:30:56.518 534 22447 E ResolverController: No valid NAT64 prefix (105, <unspecified>/0)
02-17 18:30:56.518 534 22446 E ResolverController: No valid NAT64 prefix (105, <unspecified>/0)
02-17 18:30:56.597 564 595 E libPowerHal: perfLockRel handle:294
02-17 18:30:56.716 1204 1687 E WindowManager: App trying to use insecure INPUT_FEATURE_NO_INPUT_CHANNEL flag. Ignoring
02-17 18:30:56.716 534 22467 E ResolverController: No valid NAT64 prefix (105, <unspecified>/0)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: FATAL EXCEPTION: create_react_context
02-17 18:30:56.720 22398 22454 E AndroidRuntime: Process: com.blackhedge, PID: 22398
02-17 18:30:56.720 22398 22454 E AndroidRuntime: java.lang.RuntimeException: Unable to load script. Make sure you're either running Metro (run 'npx react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:239)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:29)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:268)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1371)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:136)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1065)
02-17 18:30:56.720 22398 22454 E AndroidRuntime: at java.lang.Thread.run(Thread.java:919)
02-17 18:30:56.730 22398 22457 E fullstory: Destroy scanner called twice
02-17 18:30:56.809 1204 1329 E InputDispatcher: channel '81fad7a com.blackhedge/com.blackhedge.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
02-17 18:30:56.812 4731 4790 E PowerKeeper.Event: oops, parse AM_RESTART_ACTIVITY_AI parameter error
02-17 18:30:56.814 1204 1343 E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.927) failed {.code = ERROR_NOT_SUPPORTED, .description = }
02-17 18:30:57.182 1705 1705 E Launcher: changeViewByFsGestureState, view=ShortcutMenuLayer, alpha=1.0, scale=1.0
02-17 18:30:57.233 564 595 E libPowerHal: perfLockRel handle:295
02-17 18:30:59.825 1204 1343 E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.927) failed {.code = ERROR_NOT_SUPPORTED, .description = }
I tried generating logs and searched on internet the errors i was getting on logs but found nothing

this error is caused by the absence of the index.android.bundle file in the ./android/app/src/main/assets directory
First step:
Create the assets folder if it does not exist in the android/app/src/main/ directory
Second step:
Run the following command line:
react-native bundle --platform android --dev false --entry-file index.js --bundle-output ./android/app/src/main/assets/index.android.bundle --assets-dest ./android/app/src/main/res/
Step three:
Compile the application in release mode

GasService in android logcat

I've got a few errors in my logcat that keep on repeating every second or so, but I don't understand where they come from ?
1539 1547 E GED : Failed to execute ioctl 3222824709, BridgeID(5), err(-1)
1539 1547 E GasService: Error on query GED info, err=1
1539 1547 E GED : Failed to execute ioctl 3222824709, BridgeID(5), err(-1)
1539 1547 E GasService: Error on query GED info, err=1
1060 1161 E ApplockRunningService.TAG: AppLockService------------->tasks = [android.app.ActivityManager$RunningTaskInfo#40598b4]
1060 1161 E ApplockRunningService.TAG: AppLockService------------->packname = com.android.launcher3
1060 1161 E ApplockRunningService.TAG: getLockFlag------------> c = android.content.ContentResolver$CursorWrapperInner#a210cdd
When listing the android services, there is no such "GasService";
there is also no "Gas" process listed with "ps".
Additional info: the process 1539 is launched by /vendor/bin/ged_srv
which is a binary file that is not visible except by root :-/
So, where do these errors come from ?
Thank you !

GasService see => GpuAppSpectatorService
native:
/system/bin/gas_srv
/system/lib/libgas.so
pkg:
com.mediatek.GpuAppSpectatorService
init:
on property:sys.boot_completed=1
start gas_srv
service gas_srv /system/bin/gas_srv
class core
user system
group system
disabled
se policy:
/system/bin/gas_srv u:object_r:gas_srv_exec:s0

Run an android emulator on a headless server

I have a headless Debian server that I used to use for CI and testing. I don't know what happened but it broke, so I removed the whole SDK and started from scratch.
I did:
Retrieve the latest URL with:
curl -s 'https://developer.android.com/studio/index.html#downloads' \
| grep -oP 'https?://dl.google.com/android/repository/sdk-tools-linux[^" ]+' \
| sort | uniq
downloaded it & unzipped it
updated the SDK manager:
./tools/bin/sdkmanager --update
accepted the licenses:
yes | ./tools/bin/sdkmanager --licenses
installed everything for API level 27:
./tools/bin/sdkmanager --install "platforms;android-27" "system-images;android-27;google_apis;x86"
I have installed KVM and Qemu according to the instructions
I have created an AVD with:
echo no | ./tools/bin/avdmanager create avd --force --name avdname -k "system-images;android-27;google_apis;x86"
then started the emulator:
./emulator/emulator #avdname -no-window
It starts but in logcat it complains about the lack of Qemu:
01-09 23:15:19.278 4075 4075 D libEGL : Emulator has vendor provided software renderer, qemu.gles is set to 2.
01-09 23:15:19.282 4075 4075 D libEGL : loaded /vendor/lib/egl/libEGL_emulation.so
01-09 23:15:19.283 4075 4075 D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_emulation.so
01-09 23:15:19.288 4075 4075 D libEGL : loaded /vendor/lib/egl/libGLESv2_emulation.so
01-09 23:15:19.294 4075 4075 E : connect: failed with fd -1 errno 22
01-09 23:15:19.294 4075 4075 E : Failed to connect to host (QemuPipeStream)!!!
01-09 23:15:19.294 4075 4075 E EGL_emulation: Failed to establish connection with the host
01-09 23:15:19.294 4075 4075 W libEGL : eglInitialize(0xab2fb014) failed (EGL_SUCCESS)
01-09 23:15:19.295 4075 4075 I /system/bin/surfaceflinger: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
01-09 23:15:19.295 4075 4075 E EGL_emulation: tid 4075: eglGetConfigs(774): error 0x3001 (EGL_NOT_INITIALIZED)
01-09 23:15:19.295 4075 4075 E EGL_emulation: tid 4075: eglChooseConfig(796): error 0x3001 (EGL_NOT_INITIALIZED)
01-09 23:15:19.295 4075 4075 E EGL_emulation: tid 4075: eglGetConfigs(774): error 0x3001 (EGL_NOT_INITIALIZED)
01-09 23:15:19.295 4075 4075 E EGL_emulation: tid 4075: eglChooseConfig(796): error 0x3001 (EGL_NOT_INITIALIZED)
01-09 23:15:19.295 4075 4075 W SurfaceFlinger: no suitable EGLConfig found, trying a simpler query
01-09 23:15:19.296 4075 4075 E EGL_emulation: tid 4075: eglGetConfigs(774): error 0x3001 (EGL_NOT_INITIALIZED)
01-09 23:15:19.296 4075 4075 E EGL_emulation: tid 4075: eglChooseConfig(796): error 0x3001 (EGL_NOT_INITIALIZED)
01-09 23:15:19.296 4075 4075 F SurfaceFlinger: no suitable EGLConfig found, giving up
01-09 23:15:19.296 4075 4075 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 4075 (surfaceflinger), pid 4075 (surfaceflinger)
01-09 23:15:19.305 4086 4086 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
01-09 23:15:19.306 1592 1592 I /system/bin/tombstoned: received crash request for pid 4075
01-09 23:15:19.307 4086 4086 I crash_dump32: performing dump of process 4075 (target tid = 4075)
I have hw.gpu.enabled = false, not sure if it is relevant.
KVM is happy:
$ ./tools/emulator -accel-check
accel:
0
KVM (version 12) is installed and usable.
accel
I don't know if KVM is the issue or if the GPU acceleration is something else.
Interestingly, this works like a charm:
./tools/bin/sdkmanager --install "system-images;android-26;google_apis;x86_64" "platforms;android-26"
echo no | ./tools/bin/avdmanager create avd --force --name avd26 -k "system-images;android-26;google_apis;x86_64"
./emulator/emulator #avd26 -no-window
Is it because it's an x86_64 image? Because the API 27 system image is buggy? Why isn't there a 64 bit image for API 27 b the way?

Try -gpu swiftshader. This seems to fix the issue for me.

try running the emulator with these params in addition to the -no-window param:
qemu -enable-kvm -snapshot
I had similar issues starting the emulators recently in a headless environment and this helped me resolve it. System image version should not matter.

Android O HIDL not available

I have problem with Android O HIDL. The failure log shows it can't find out the service.
However I can see it by adb shell ps -A | grep fingerprint
system 18758 1 17408 3276 pipe_wait 7c79e93e08 R android.hardware.biometrics.fingerprint#2.1-service`
Could anyone give me a hint how to solve the problem? I checked https://source.android.com/devices/architecture/hidl/ but could not get the solution.
Error log:
08-21 06:00:35.864 1890 2264 V FingerprintService: mDeamon was null, reconnect to fingerprint
08-21 06:00:35.864 1890 2264 I system_server: Looking for service android.hardware.biometrics.fingerprint#2.1::IBiometricsFingerprint/default
08-21 06:00:35.864 2240 2240 D wpa_supplicant: nl80211: Set mode ifindex 24 iftype 2 (STATION)
08-21 06:00:35.866 566 566 W /system/bin/hwservicemanager: getTransportFromManifest: Cannot find entry android.hardware.biometrics.fingerprint#2.1::IBiometricsFingerprint in either framework or device manifest, using default transport.
08-21 06:00:35.866 1890 2264 E system_server: service android.hardware.biometrics.fingerprint#2.1::IBiometricsFingerprint declares transport method EMPTY but framework expects hwbinder.
08-21 06:00:35.867 1890 2264 E FingerprintService: Failed to get biometric interface
08-21 06:00:35.867 1890 2264 E FingerprintService: android.os.RemoteException: HwBinder Error: (-2147483648)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.os.HwBinder.getService(Native Method)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.hardware.biometrics.fingerprint.V2_1.IBiometricsFingerprint.getService(IBiometricsFingerprint.java:44)
08-21 06:00:35.867 1890 2264 E FingerprintService: at com.android.server.fingerprint.FingerprintService.getFingerprintDaemon(FingerprintService.java:239)
08-21 06:00:35.867 1890 2264 E FingerprintService: at com.android.server.fingerprint.FingerprintService$FingerprintServiceWrapper.isHardwareDetected(FingerprintService.java:1198)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.hardware.fingerprint.IFingerprintService$Stub.onTransact(IFingerprintService.java:156)
08-21 06:00:35.867 1890 2264 E FingerprintService: at android.os.Binder.execTransact(Binder.java:674)
08-21 06:00:35.867 1890 2264 W FingerprintService: fingerprint HIDL not available

I've succeeded in running my fingerprint HAL on Android 8.1 executing on HiKey
96 board after modified files as below.
Firstly, it's necessary that adding HIDL configures to declare a device as a vendor or you would get VTS failed.
About HIDL configures
device/linaro/hikey/manifest.xml
+<hal format="hidl">
<name>android.hardware.biometrics.fingerprint</name>
<transport>hwbinder</transport>
<version>2.1</version>
<interface>
<name>IBiometricsFingerprint</name>
<instance>default</instance>
</interface>
</hal>
Secondly, finger service will be started after you define it in the file below.
device/linaro/hikey/device-common.mk
+#init finger service and copy
android.hardware.biometrics.fingerprint#2.1-service.rc to
system/vendor/etc/init
+PRODUCT_PACKAGES += \
+android.hardware.biometrics.fingerprint#2.1-service
+# copy permission file of finger service
+PRODUCT_COPY_FILES += \
+frameworks/native/data/etc/android.hardware.fingerprint.xml:system/etc
/permissions/android.hardware.fingerprint.xml
Finally, check finger service has been started and running in Android system by using terminal commands such as "adb shell" and "ps | grep finger".
Any suggestion is welcome.

I found out that I need to add the code to the manifest.xml
(Ref. https://source.android.com/devices/architecture/vintf/objects )
<hal format="hidl">
<name>android.hardware.biometrics.fingerprint</name>
<transport>hwbinder</transport>
<impl level="generic"></impl>
<version>2.1</version>
<interface>
<name>IBiometricsFingerprint</name>
<instance>default</instance>
</interface>
</hal>

Tango Unity examples crashing when built with Unity 2017.1

I just installed Unity 2017.1.0f3 and tried to compile the examples but all of them crash at start on my Lenovo Phab 2 Pro (Tango version 1.55).
I loaded the project tango-examples-unity\UnityExamples in Unity without modifying it and Unity converts it to the Unity 2017.1.0f3 version. The building seems to run fine but on the phone the resulting app crashes at start.
Everything worked fine for me on Unity 5.6. Maybe the Tango SDK is simply not supported yet by Unity 2017.1 but I could not find any information on that.
Here are the console output on Unity after building the app and the logs of the Tango when I launch the app and it crashes.
Unity console output
Tango Logs :
07-13 18:26:07.867 1261-1409/? W/BroadcastQueue: Permission Denial: broadcasting Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } from com.android.launcher3 (pid=4828, uid=10025) requires com.google.android.launcher.permission.RECEIVE_LAUNCH_BROADCASTS due to receiver com.google.android.gms/.icing.proxy.ApplicationLauncherReceiver
07-13 18:26:07.868 1261-1409/? W/BroadcastQueue: Permission Denial: receiving Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$GmsExternalReceiver requires com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS due to sender com.android.launcher3 (uid 10025)
07-13 18:26:07.882 544-3682/? E/audio_route: audio_route_apply_and_update_path:name(speaker-protected)
07-13 18:26:07.882 544-3682/? E/audio_route: audio_route_apply_and_update_path:name(vi-feedback)
07-13 18:26:07.882 544-3682/? E/voice: voice_is_in_call_rec_stream: input stream is NULL
07-13 18:26:07.883 544-3682/? E/ACDB-LOADER: Error: ACDB AudProc vol returned = -19
07-13 18:26:07.883 544-3682/? E/audio_route: audio_route_apply_and_update_path:name(spkr-vi-record)
07-13 18:26:07.894 544-3682/? E/voice: voice_is_in_call_rec_stream: input stream is NULL
07-13 18:26:07.894 544-3682/? E/ACDB-LOADER: Error: ACDB_CMD_GET_AUDPROC_COMMON_TABLE_SIZE Returned = -19
07-13 18:26:07.894 544-3682/? E/ACDB-LOADER: Error: ACDB audproc returned = -19
07-13 18:26:07.894 544-3682/? E/ACDB-LOADER: Error: ACDB AudProc vol returned = -19
07-13 18:26:07.894 544-3682/? E/ACDB-LOADER: Error: ACDB AFE returned = -19
07-13 18:26:07.895 544-3682/? E/audio_route: audio_route_apply_and_update_path:name(low-latency-playback speaker-protected)
07-13 18:26:07.936 8061-8061/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.projecttango.unityexamples, PID: 8061
java.lang.Error: FATAL EXCEPTION [main]
Unity version : 2017.1.0f3
Device model : LENOVO Lenovo PB2-690M
Device fingerprint: Lenovo/phinny_row/PB2PRO:6.0.1/MMB29M/PB2-690M_S200100_170228:user/release-keys
Caused by: java.lang.NoSuchMethodError: No direct method <init>(Landroid/content/ContextWrapper;)V in class Lcom/unity3d/player/UnityPlayer; or its super classes (declaration of 'com.unity3d.player.UnityPlayer' appears in /data/app/com.projecttango.unityexamples-2/base.apk)
at com.google.unity.GoogleUnityActivity.onCreate(GoogleUnityActivity.java:106)
at android.app.Activity.performCreate(Activity.java:6285)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1108)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2370)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2477)
at android.app.ActivityThread.access$900(ActivityThread.java:150)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5418)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-13 18:26:07.938 1261-4787/? W/ActivityManager: Force finishing activity com.projecttango.unityexamples/com.google.unity.GoogleUnityActivity
07-13 18:26:08.290 1261-1453/? E/WallpaperManagerService: onEvent:settings_system.xml.bak,changedFile:/data/system/users/0/settings_system.xml.bak
07-13 18:26:08.294 1261-1453/? E/WallpaperManagerService: onEvent:settings_system.xml,changedFile:/data/system/users/0/settings_system.xml
07-13 18:26:08.294 1261-1453/? E/WallpaperManagerService: onEvent:settings_system.xml.bak,changedFile:/data/system/users/0/settings_system.xml.bak
07-13 18:26:08.545 1261-1409/? W/ActivityManager: Activity pause timeout for ActivityRecord{e8388eb u0 com.projecttango.unityexamples/com.google.unity.GoogleUnityActivity t822 f}

After testing it has been confirmed that Unity 2017.1 is currently not supported by the Tango SDK, we only support Unity 5.6 at this time.