After updating app in android 12 and try to run app in android 12 device and simulator facing issue for crashing.
Here is issue.
androidx.media.session.MediaButtonReceiver: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present'
Resolve
With use of android:exported="true" fixed issue for run app but service not start once player on in app. so again crash app.
Please check the Github for React-Native-Track-Player.
There is a Beta version for use with Android 12.
Following this question, anyone was able to patch the package to make it work on Android 12? Using a non-final version seems more buggy than just adapting the stable one.
Related
I was building a react native project and got an upgrade message when I run "yarn run ios":
simctl[5640:1381079] CoreSimulator detected version change. Framework version (857.14) does not match existing job version (857.13). Attempting to remove the stale service in order to add the expected version. error Could not get the simulator list from Xcode. Please open Xcode and try running project directly from there to resolve the remaining issues. SyntaxError: Unexpected token I in JSON at position 0、
However, after this upgrade, there is something wrong with my project. Any suggestion how to back to the old version?
I tried to use other version of ios simulator and tried to clean the xcode build, but its not help.
I ran into a similar issue. The trick was
Quit all iOS simulators
Let Xcode install the newest iOS simulators
Run the project from the Xcode workspace.
After that I was able to start the simulator again from npx react-native run-ios --simulator='iPhone 14' or yarn run iOS
I have installed 'react-native-admob-native-ads' plugin with 0.4.1 version and react-native version is 0.64.2.
i can't test ad without testAdId in Android,
iOS we can't test with testAdId in simulator.
any one can help me to figure this out?
unfortunately, current can't use Ad on react-native.
https://github.com/invertase/react-native-firebase/issues/5329#issuecomment-843272057
We have recently updated our react-native project to 0.62.2. To perform the linking we need to update the realm version to 6.0.0. It is working fine on ios but it is crashing on android 10 only. Below android 10 it is also working fine. We have realm version 0f 0.29.2 initially. After that we again degraded the version of realm to 0.29.2 then it is working fine. We have also updated the version above 6 also but the same problem occurs.
How can we update our realm to 6.0.0 or any version above it for android 10?
i am new to react native
i followed the instructions on facebook react-native site to install java, Android Studio, SDK and SDK tools
the emulator is up and running , paths are correct. but when running the app i get
FAILURE: Build failed with an exception.
What went wrong: A problem occurred configuring project ':app'.
Failed to notify project evaluation listener.
javax/xml/bind/annotation/XmlSchema
the same app IOS runs , i even tried Android USB debugging
help please
anyone?
The problem was Java 9. even though react-native site asks you to install Java SDK 8 or later , then 9 installation doesn't work for some reason. I uninstalled 9 and installed 8 and it worked like a charm
This normally happens when the JDK is not correctly installed or the JAVA_HOME has not properly been set. Make sure to export your JAVA_HOME path. and have a working JDK version running on your computer.
I upgraded to react-native 0.16.0-rc, ran npm install, then ran react-native upgrade. When trying to launch the iOS app in a simulator (or device, doesn't matter) I get the error:
[error][tid:com.facebook.React.RCTExceptionsManagerQueue] Unhandled JS Exception: babelHelpers.interopRequireDefault is not a function. (In 'babelHelpers.interopRequireDefault(_reactNative)', 'babelHelpers.interopRequireDefault' is undefined)
I've just about run out of ideas here. Is there something I need to add to my xcode project maybe? Merging the latest react-native templates into mine was a nightmare so maybe something got messed up there.
This problem is discussed in this Github issue and fixed by this commit. You can apply this patch temporarily until it is merged into the project with the version 0.16.