Error in USB debugging live testing in React Native - react-native

I am new to React Native and I install React Native and I want to test using y device (Realme 2).
Using USB debugging, but I am stuck on this same mobile using Android Studio runs in ADB.
This stucks at this position I await multiple 15m
info Starting JS server...
info Installing the app...
Configure project :app
File C:\Users\Muhammed Sajid Ali.android\repositories.cfg could not be loaded.
Checking the license for package Android SDK Platform 28 in D:\sajid\AndroidSdk\licenses
License for package Android SDK Platform 28 accepted.
Preparing "Install Android SDK Platform 28 (revision: 6)".
<======-------> 50% CONFIGURING [15m 0s]
:app

I solved this.
I earlier installed the Android SDK 8, 7.4.4, and 9 versions, but my mobile was 8.1. That’s why
it didn't start and it was downloading SDK 8.1. As I saw in the Android SDK folder, there was a new folder with some files.
Then I downloaded the 8.1 SDK, and it ran perfectly.

I think that was no problem with your compiler behavior, but I can suggest you to check if installing the app from USB is permitted in your phone's developer option and try to trigger the compiler with pressing return key (or enter) on the command line. That was working on mine.

Related

Windows 10 WSL2 expo cannot find simulated android device from Android Studio

I am new to android development and am trying to learn react-native by following a tutorial here. The problem is whenever I try to start my react-native project within my simulated android device, expo cli cannot find it. This step is at the 25 minute mark of the video and my progress can be summarized as follows:
I have react-native on my machine and have installed expo cli
I've downloaded Android Studio which is located: C:\Users..\AppData\Local\Android\Sdk
I have my emulated android device up and running via Virtual Device
Manager
After typinng "npm start" When I type "a" within the terminal of WSL to run this app on my virtual android device I get the following message when it tries to open the emulator:
No Android connected device found, and no emulators could be started
automatically. Please connect a device or create an emulator
(https://docs.expo.dev/workflow/android-studio-emulator).
At which point my expo developer tools browser window displays that
Expo Developer Tools is disconnected from Expo CLI. Use the expo start
command to start the CLI again
When I goto the terminal and do this, it just restarts this failure over again when I type "a" to start my app in the simulated android device. Some of the solutions I've tried are:
following the documentation on the workflow android studio emulator link. I find though that all of the options within my version of android studio look drastically different, and that my file location is much different than what they have listed.
uninstalling and reinstalling Android Studio
Making sure SDK tools is checked as per this stack overflow post
following the instructions in this stack overflow post, however I am not trying to connect a phone via usb so this does not help me.
My setup is as follows:
OS: Windows 10
VM: WSL2 Ubuntu 20.04.3 LTS
Text Editor: Visual Studio Code 1.63.2
Android Studio: BumbleBee 2021.1.1
Expo CLI version: 5.0.3
here are some screen shots:
^ that one is right before I try to type "a" within the expo cli within terminal.

This release is not compliant with the Google Play 64-bit requirement (ExpoKit)

Warning in Google Play:
This release is not compliant with the Google Play 64-bit requirement
The following APKs or App Bundles are available to 64-bit devices, but they only have 32-bit native code: 1.
From August 1, 2019 all releases must be compliant with the Google Play 64-bit requirement.
Include 64-bit and 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives only the native code it needs. This avoids increasing the overall size of your app.
How to fix this problem?
What I have already tried is to add ndk.abiFilters in gradle
ndk.abiFilters 'armeabi-v7a','arm64-v8a','x86','x86_64'
when I created apk, app started crashing immediately.
You have to upgrade your react native. For expo follow react native docs. For react native without expo You can use these commands:
sudo npm install -g react-native-git-upgrade
Then
react-native-git-upgrade

How to fix Play Store error about 64 bit binaries when publishing app built Expo / React Native?

I am deploying an app built with React Native and Expo to Play Store and the following error appears:
This release is not compliant with the Play 64-bit requirement.
The following APKs or App Bundles are available to 64-bit devices, but they have only 32-bit native code: 1. From 1 de agosto de 2019 all releases must be compliant with the Play 64-bit requirement.Include 64-bit native code in addition to 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives just the native code it needs.
My Expo version is 27.0.1
Regarding this post https://github.com/facebook/react-native/issues/2814 react-native v0.59 is 64bit compliant (https://facebook.github.io/react-native/blog/2019/03/12/releasing-react-native-059)
and Expo 27 support react-native v0.55.
I'm not an expert with Expo, but can you manually upgrade react-native to v0.59 ? or maybe wait a new version of Expo ?
On July 16th 2019 they stated in 64-Bit Support and Android App Bundles:
We want to let you know that you can now build 64-bit support-enabled .apks that also make use of Android App Bundles (AABs) with SDK33 projects and, of course, with SDK34 upon its release. (Since SDK33 is the first Expo SDK version that uses React Native 0.59, the React Native version that allows for 64-bit support, prior versions of the SDK can’t be updated.)
These updates help us support your new submissions to the Google Play store, which will need to have 64-bit support starting August 1st. Your existing apps won’t need to upgrade to include 64-bit until you need to submit your next app update (though SDK33 has a lot of other fun things you might enjoy!).
Ensure you are running the latest version of expo-cli by running yarn global add expo-cli or npm install -g expo-cli.
Currently, there is no way to fix this. But the Expo Team promised ...
... to add this feature [64-bit binaries] before the deadline.
see here: https://forums.expo.io/t/does-expo-package-64-bit-version/18947

Worklight 6.1 - Error on Blackberry 10

I'm using Worklight Studio 6.1.0.00-20131219-1900 and trying to build an app for Blackberry 10
I create a new Worklight app (no customizations other than adding the blackberry 10 environment), run it on the Worklight server, and use ripple to build and deploy to the blackberry 10 simulator.
The app installs on the simulator, But when it launches, I immediately get a JavaScript error:
[ERROR] Error initializing Cordova: Extension Device not found
This is possibly related to a problem seen with Cordova 3.1 (see: Error initializing cordova: Extension device not found in PhoneGap 2.9.0 and blackberry10 webworks application) but I'm not seeing any solutions.
Is there any way to get Worklight 6.1 apps to work on Blackberry 10?
My guess is that your issue is mentioned in infocenter
http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/index.jsp?topic=%2Fcom.ibm.worklight.dev.doc%2Fdevref%2Ft_creating_a_new_ibm_BlackBerry_10_environment.html
basically, did you do the "ant qnx copy-extensions" command ?

Titanium Studio My Application does not launch in Android emulator

I am new to Titanium studio and bothered by a problem: I installed Titanium sdk 1.7.1, android 2.2,android 2.1 updates on mac 10.6.6 and I am able to successfully launch android emulator but emulator does not launch any of my application even kitchen sink example..
[INSTALL_FAILED_MISSING_SHARED_LIBRARY] - this error says that application tries to use libraries, that your system doesn't contain. In most cases it tries to use Google API's (and KitchenSink too). So open 'tiapp.xml' in your project, click 'configure...' link and under 'Android' section choose android version with Google API's in 'Default Android SDK' text box. If no version with Google API's - install it using AVD.