Mobile & Cross-Platform
145 verified issues
AsyncStorage not fulfilling promise on Android 7+
Issue I am using `redux-persist` in a react native project, that runs just fine in a broad number of devices execept Android 7. I am trying to debug the problem on why my AsyncStorage is nor persisting and found this: The following code executes inside React Native component lifecycle's [code block] Code after 'Inside setInterval' is never called. It only runs once if outside the setInterval. If I call once the code outside the setInterval it appears to run just fine. I also tried callback format vs async / await version but it does not seem to matter. Same problem I had using firebase js library (callbacks never return after the first one). I am now looking for alternatives to workaround the problem. Works with `setImmediate` and `InteractionManager.runAfterInteractions`. Seems that `redux-persist` uses `setImmediate` or fallsback to `setTimeout`. Any ideas? Additional Information React Native version: React Native 0.40+ (last tested on RN@0.44) Platform: Only Android 7 and above Development Operating System: Mac os, Node 7.4 Dev tools: [code block] In case this is a user level question I opened a question on stackoverflow, no luck yet, https://stackoverflow.com/questions/44114061/asyncstorage-is-not-returning-the-callback?noredirect=1#comment75248695_44114061
Duplicated letters when autoCapitalize="characters" on android
Description When trying to implement an upper case only input, adding `autoCapitalize="characters"` seems to work on Android by setting the keyboard to be upper case by default. One can hit the shift key and then type a lower case letter. To ensure that we only let the user enter (and see) upper case letters, I thought that I might be able to handle it by ensuring that when we update the react state of the component we capture the text in upper case. By using a toUpperCase on top of what is a pretty standard state update cycle (i.e. a very similar update method ala the examples at https://facebook.github.io/react-native/releases/next/docs/textinput.html ), this saves the input into the state, uppercased, ready for the next render cycle. (I'm not concerned about the dangers of toUpperCase at this point.) Unfortunately, the behaviour is a bit strange when you start typing both upper and lowercase letters, where you start getting repeated letters, e.g. if I type _AbC_, I will end up with _ABABC_, _AbcdE_ I get _ABABCDABABCDE_. Reproduction I created an example app here: https://rnplay.org/apps/t-gBOA Note that the behaviour seems fine on the iOS simulator, but is 'wrong' on the android simulator. or see the component below: [code block] Solution I suspect that there's something going awry with the syncing of state between the react state and the state of the underlying components, quite possibly some case-ignoring checks are being in some places, but not others. Addit
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0)
Same as https://github.com/facebook/react-native/issues/24261 but still occuring on device Caterpillar S41 (Android 8.0). React Native version: 0.59.10 [code block]
New RN project will not build on Xcode 12.5 Beta 3
EDIT (by @kelset): Please read the current status of things at this comment. --- Description Running the latest Xcode/React Native etc. Upgrading an existing project failed so I tested with a new RN project (npx react-native init TestApp --version 0.64.0 --template react-native-template-typescript). It will build and run under Xcode 12.4, but fails when attempting to build with Xcode 12.5 Beta 3 (12E5244e). It's unlikely to be relevant, but the app is targeting an iPhone 12 Simulator running iOS 14.5 React Native version: Run `react-native info` in your terminal and copy the results here. [code block] Steps To Reproduce Provide a detailed list of steps that reproduce the issue. 1. Install the above tools, Xcode 12.5 Beta 3, RN 0.64.0 etc. 2. Create a new app (npx react-native init TestApp --version 0.64.0 --template react-native-template-typescript) 3. [code block] 3. [code block] then [code block] 4. [code block] 5. This error also appears if you replace step 4 with launching Xcode.app and building the app that way Expected Results Describe what you expected to happen. A successful build of the example app, running on the simulator. Snack, code example, screenshot, or link to a repository: Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. You may provide a screenshot of the application if you think it is relevant to your bug report. Here are some tips for providing a min
[0.60.3] App crash on startup when enabling Hermes (enableHermes: true)
App is crashing when I enable Hermes in android/app/build.gradle. App is working fine with react-native 0.60.3 with enableHermes: false Error: ` 07-12 08:06:59.097 20330-20330/com.reactnativememoryprofile E/SoLoader: couldn't find DSO to load: libjscexecutor.so 07-12 08:06:59.123 20330-20345/com.reactnativememoryprofile E/SoLoader: couldn't find DSO to load: libhermes.so 07-12 08:06:59.124 20330-20345/com.reactnativememoryprofile E/AndroidRuntime: FATAL EXCEPTION: create_react_context Process: com.reactnativememoryprofile, PID: 20330 java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738) at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529) at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484) at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20) at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:27) at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949) at java.lang.Thread.run(Thread.java:818) ` React Native version: System: OS: macOS 10.14.5 CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Memory: 373.31 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 10.15.1 - /usr/local/bin/node
Support third-party 64-bit libraries on Android
Excerpt from the Android Developers Blog article, Get your apps ready for the 64-bit requirement: [added by @hramos] The 64-bit requirement: what it means for developers Starting August 1, 2019: All new apps and app updates that include native code are required to provide 64-bit versions in addition to 32-bit versions when publishing to Google Play. Extension: Google Play will continue to accept 32-bit only updates to existing games that use Unity 5.6 or older until August 2021. Starting August 1, 2021: Google Play will stop serving apps without 64-bit versions on 64-bit capable devices, meaning they will no longer be available in the Play Store on those devices. This will include games built with Unity 5.6 or older. The requirement does not apply to: APKs or app bundles explicitly targeting Wear OS or Android TV, which are form factors that do not currently support 64-bit code. APKs or app bundles that are not distributed to devices running Android 9 Pie or later. Original Issue Hey, it appears that React Native on Android doesn't provide a 64-bit version of the `libreactnativejni.so` native library, which can cause compatibility issues on 64-bit devices. I ran into this while attempting to integrate React Native with a large existing application I'm developing. Steps to reproduce: 1. Create a new application with `react-native init`. 2. In the "android/app/build.gradle" file, add `compile 'io.realm:realm-android:0.82.2'` to the end of the `dependencies {}` b
Image cannot show image in iOS 14
Image cannot show image in iOS 14, but can show location, like: <Image source={ require('./images/add_scan_images.png') } /> Environment: Xcode Version 12.0 beta (12A6159) Simulator: IPhone SE - 2nd generation - 14.0 "react": "16.11.0", "react-native": "0.62.2"
[Master Task] Print: Entry, ":CFBundleIdentifier", Does Not Exist
Please see #21303 to understand why you're running into this (_Edited by @hramos - the original issue text has been replaced with a description of the problem_) Description This issue describes a class of failures where the iOS build fails with the following output: [code block] This error message is a red herring as the problem is not actually caused by a missing `:CFBundleIdentifier` entry. What this output means is that your iOS project could not be built successfully. If you are encountering this issue, please try the following: 1. Upgrade to the latest React Native release. 2. Upgrade to the latest Xcode version. 3. Read through the Getting Started guide if you haven't in a while, and make sure your development environment is up to date. 4. Try building your project again. If none of these resolve your issue, please read through this thread to learn about what has worked for others. Please refrain from adding "me too" comments unless you have material information that contributes to others' solutions.
π£ Using React Hooks in React Native
React Hooks will ship as part of React Native 0.59. If you are interested in using Hooks before then, see my comment below. Original issue: --- - [x] Review the documentation: https://facebook.github.io/react-native - [x] Search for existing issues: https://github.com/facebook/react-native/issues - [x] Use the latest React Native release: https://github.com/facebook/react-native/releases Environment [skip envinfo] OS: Windows 10 Node: 10.11.0 Yarn: Not Found npm: 6.4.1 Watchman: Not Found Xcode: N/A Android Studio: Version 3.2.0.0 AI-181.5540.7.32.5056338 Packages: (wanted => installed) react: 16.7.0-alpha.0 => 16.7.0-alpha.0 react-native: https://github.com/expo/react-native/archive/sdk-30.0.0.tar.gz => 0.55.4 expo: 2.2.0 Description When using React Hooks like `useState` within a function component, I get the following error message. > hooks can only be called inside the body of a function component [code block]
[Android] Error: Duplicate resources
- [x] Review the documentation: https://facebook.github.io/react-native - [x] Search for existing issues: https://github.com/facebook/react-native/issues - [x] Use the latest React Native release: https://github.com/facebook/react-native/releases Environment React Native Environment Info: System: OS: macOS 10.14 CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz Memory: 103.10 MB / 8.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 8.12.0 - /usr/local/bin/node Yarn: 1.0.1 - /usr/local/bin/yarn npm: 6.4.1 - /usr/local/bin/npm Watchman: 4.7.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1 Android SDK: API Levels: 16, 17, 19, 21, 23, 24, 25, 26, 27, 28 Build Tools: 19.1.0, 20.0.0, 23.0.1, 23.0.2, 23.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.3, 28.0.0, 28.0.0, 28.0.2, 28.0.3 System Images: android-16 | ARM EABI v7a, android-16 | MIPS, android-16 | Intel x86 Atom, android-16 | Google APIs Intel x86 Atom, android-19 | Google APIs Intel x86 Atom, android-24 | Google Play Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-P | Google APIs Intel x86 Atom, android-P | Google Play Intel x86 Atom IDE
"__nw_connection_get_connected_socket_block_invoke Connection has no connected handler" in logs
Workaround _Edit by @hramos, maintainer:_ Several solutions have been presented in this thread: `OS_ACTIVITY_MODE` @HADB proposed: 1. Open Xcode. 2. Open Product menu. 3. Select Edit Scheme... 4. Add the following under Environment Variables: Name: `OS_ACTIVITY_MODE` Value: `disable` 5. Run your app again Using `react-devtools` Alternatively, ensure `react-devtools` is installed on your system. Resolution This is a known issue in the iOS Simulator. The issue will remain open to increase visibility. We are limited comments on this thread to core contributors. Pull requests with proposed fixes are welcome. Original Issue ENV RN 0.32 iOS 10, iPhone 6 Plus Problem The console of Xcode continue print "__nw_connection_get_connected_socket_block_invoke 6 Connection has no connected handler". Screen
Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported.
Similar to #1693. It seems to be an issue with the `Touchable` component with Chrome Debugging on React Native 0.19.0. [code block] The code that produces this error is from a freshly started application using a TouchHighlight component: [code block] P.S. Is there a better way to copy a stacktrace? I'm just copying from the Chrome dev tools console
RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks
I randomly get this warning at iOS app start (i.e. not always). Is this a bug report? Yes Have you read the Contributing Guidelines? Yes Environment OS: macOS Sierra 10.12.6 Node: 6.10.2 Yarn: 1.0.2 npm: 5.4.2 Watchman: 4.7.0 Xcode: Xcode 9.0 Build version 9A235 Android Studio: 2.1 AI-143.2915827 Packages: (wanted => installed) react: ^16.0.0 => 16.0.0 react-native: ^0.49.3 => 0.49.3 Steps to Reproduce 1. Start the app Expected Behavior No warning Actual Behavior <img width="432" alt="capture d ecran 2017-10-15 12 49 45" src="https://user-images.githubusercontent.com/160279/31584109-0fc35620-b1a8-11e7-88c2-cbbdd383fc84.png"> Reproducible Demo N/A Some packages I use https://github.com/antoinerousseau/react-native-custom-components https://github.com/rebeccahughes/react-native-device-info https://github.com/evollu/react-native-fcm https://github.com/gwmccull/react-native-polyfill https://github.com/getsentry/react-native-sentry
No bundle url present
Description I noticed some people recently asking about this "No bundle url present" error and I just faced it myself. Reproduction I had just run Λreact-native init projectNameΛ, setup my App.js file (a simple Hello World), called it in both iOS and Android indexes and run Λreact-native run-iosΛ. Then the No bundle url present error appeared. Solution I tried to delete my node_modules and npm install, close the packager and run the project again, but it could only be solved when I follow the steps given here (http://stackoverflow.com/questions/42610070/what-means-of-no-bundle-url-present-in-react-native). Run "react-native run-ios" When the error appears, run "npm install" * Then run "react-native run-ios" again. Additional Information This is the first project I started using RN 0.42. Since it never happened before and I am not the only one facing this issue, I guess it should be taken a closer look to it. Here's my package.json: [code block] If I can be more helpful to make any further test, it would be a pleasure.
Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). When Upgrading To React Native v0.70
Description Upgrade from 0.68.1 to 0.70.0. Builds fine in Xcode. Launches Simulator. Splash screen for app appears. and then it crashes with the error: ERROR Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter. A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes Version 0.70.0 Output of `npx react-native info` ystem: OS: macOS 12.3.1 CPU: (4) x64 Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz Memory: 1.20 GB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 16.15.0 - /usr/local/bin/node Yarn: Not Found npm: 8.5.5 - /usr/local/bin/npm Watchman: 2022.03.21.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5 Android SDK: Not Found IDEs: Android Studio: Not Found Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild Languages: Java: Not Found npmPackages: @react-native-community/cli: Not Found react: N
Android build failed: 'Failed to list versions for com.facebook.react:react-native.'
Description What went wrong: Could not determine the dependencies of task ':app:compileDebugKotlin'. > Could not resolve all files for configuration ':app:debugRuntimeClasspath'. > Could not resolve com.facebook.react:react-native:+. Required by: project :app project :app > project :react-native-push-notification project :app > project :react-native-code-push project :app > project :react-native-async-storage_async-storage project :app > project :react-native-community_blur project :app > project :react-native-community_clipboard project :app > project :react-native-community_datetimepicker project :app > project :react-native-community_masked-view project :app > project :react-native-community_netinfo project :app > project :react-native-community_picker project :app > project :react-native-firebase_analytics project :app > project :react-native-firebase_app project :app > project :react-native-firebase_crashlytics project :app > project :sumsub_react-native-mobilesdk-module project :app > project :react-native-action-sheet project :app > project :react-native-appsflyer project :app > project :react-native-camera project :app > project :react-native-config project :app > project :react-native-device-info project :app > project :react-native-fbsdk-next project :app > project :reac
React Native 0.62.* [TypeError: Network request failed] on file upload
Please provide all the information requested. Issues that do not follow this format are likely to stall. Description After upgrading from 0.61.4 to 0.62.0 the app will not upload files anymore from Android (all other requests are working fine) React Native version: 0.62.0 Steps To Reproduce 1. Install a fresh ReactNative app via CLI 2. Upload a file to the emulator 3. Try to upload a file using `fetch` [code block] Expected Results The request should reach the server to upload the file Snack, code example, screenshot, or link to a repository: https://snack.expo.io/01W!bybf_ [code block]
[FlatList] FlatList and VirtualizedList Scroll performance is laggy after 30+ rows .
Description Flatlist or VirtualizedList Scroll lags horribly after 30-40 rows . I am fetching the same data on onEndReached . Upto 30 rows its looks fine , but after that scrolling drops several frames . When I disable virtualization , scroll becomes normal but but responsiveness goes away . I tried disabling virtualizing on scrolling velocity this way . isVirtualizationTrue(e){ var dOffset=(e.nativeEvent.contentOffset.y- this.state.lastOffset) var dt=(e.timeStamp-this.state.lastTimeStamp) var velocity = dOffset/dt var isInstant=velocity-this.state.lastVelocity>.01 if(velocity<1 && !isInstant){ return false } if(velocity>1){ return true } if(velocity <.25){ return true } } But again , there's problem for the unmounted Component that are removed from the views , which takes long time to show up again . Is there any way to improve the scroll performance ? Here's my sample code <FlatList shouldItemUpdate={(props,nextProps)=> { return props.item!==nextProps.item } } onEndReached={this.onRefresh.bind(this)} onEndReachedThreshold={200} onRefresh={this.onRefresh.bind(this)} refreshing={this.props.Feed.isFetching } data={this.state.items} renderItem={this.renderItem.bind(this)} /> My data is sort
iOS: UI will be blocked when show Alert while closing Modal
When show Alert while closing Modal, the Alert dialog will disappear and the Modal will block the UI entirely even after reload, only on iOS. [code block]
Could not connect to development server on android emulator and on real device
Is this a bug report? Its an issue i am facing while running the normal Awesome Project on my system Have you read the Contributing Guidelines? Yes Environment 1. `react-native -v`: 0.47.1 2. `node -v`:8.2.1 3. `npm -v`:4.1.2 4. `yarn --version`: Then, specify: - Target Platform: Android - Development Operating System: Windows 7 - Build tools:26.0.0-rc2 Steps to Reproduce (Write your steps here:) 1.Open command prompt in Administrator Mode 2.run command: cd <directory where i want to create the project> 3.run command: react-native init <project name> 4.run command: cd <project name> 5.run command: react-native run-android this makes the package server run automatically on port 8081. But I am not able to access the package server from browser on the machine and the mobile. I tried using http://<system ip>:port/index.android.js http://localhost:port http://127.0.0.1:port => I was getting the red screen on both mobile and the emulator with following message: I tried running the project on real device and on emulator. On Both I got error: "Unable to load script from assets 'index.android.bundle' Make sure your bundle is packaged correctly or you're running a package server'. reloading i get the error: "Could not connect to development server." Then i set the host and port number on development setting on both and got the error "Could not connect to development server." Expected Behavior The project is expected to run on emulator and phone without any error. Bu
Typed routes not working in Expo 51 and Expo router
Minimal reproducible example https://github.com/alfjesus/typed-routes What platform(s) does this occur on? _No response_ Did you reproduce this issue in a development build? No (tested in Expo Go) Summary Creating a new project with `yarn create expo-app` (Expo 51) seems to have broken the typed routes for expo router. When I downgraded to Expo 50 (and `npx expo install --check`), typed routes started to working again. I guess there's something wrong with the generation of the types when the development server starts π€ Environment expo-env-info 1.2.0 environment info: System: OS: macOS 14.4.1 Shell: 5.9 - /bin/zsh Binaries: Node: 18.19.0 - /usr/local/bin/node Yarn: 1.22.21 - /opt/homebrew/bin/yarn npm: 10.2.3 - /usr/local/bin/npm Watchman: 2024.01.22.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.13.0 - /Users/anders/.rbenv/shims/pod SDKs: iOS SDK: Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4 IDEs: Android Studio: 2023.2 AI-232.10300.40.2321.11567975 Xcode: 15.3/15E204a - /usr/bin/xcodebuild npmPackages: expo: ~51.0.0 => 51.0.0 expo-router: ~3.5.10 => 3.5.10 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.74.1 => 0.74.1 react-native-web: ~0.19.10 => 0.19.11 npmGlobalPackages: eas-cli: 7.8.2 Expo Workflow: managed Expo Doctor Diagnostics β Check Expo
Error: Unable to resolve module `./debugger-ui/debuggerWorker.cff11639.js` from ``:
Please provide all the information requested. Issues that do not follow this format are likely to stall. Description Please provide a clear and concise description of what the bug is. Include screenshots if needed. Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html React Native version: [code block] Steps To Reproduce Provide a detailed list of steps that reproduce the issue. 1. run `npx react-native init Blah --template react-native-template-typescript` 2. run `npx react-native start` 3. run `npx react-native run-android` 4. Tell app to use debug mode 5. See exception: [code block] Expected Results I wouldn't get this error.
xcode 11.4 build fatal error: module map file xxx/Build/Products/Debug-iphoneos/YogaKit/YogaKit.modulemap' not found
Please provide all the information requested. Issues that do not follow this format are likely to stall. Description fatal error: module map file '/Users/miaohao/Library/Developer/Xcode/DerivedData/apex_baojia2-cdczyhhwbgshmtbdymitajpzamao/Build/Products/Debug-iphoneos/YogaKit/YogaKit.modulemap' not found React Native version: Run `react-native info` in your terminal and copy the results here. System: OS: macOS 10.15.3 CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz Memory: 219.52 MB / 8.00 GB Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.16.1 - /usr/local/bin/node Yarn: 1.22.0 - /usr/local/bin/yarn npm: 6.13.4 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.8.4 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2 Android SDK: API Levels: 23, 24, 25, 26, 27, 28, 29 Build Tools: 26.0.2, 28.0.3 System Images: android-23 | Android TV Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 3.6 AI-192.7142.36.36.6241897 Xcode: 11.4/11E146 - /usr/bin/xcodebuild Languages: Python: 2.7.16 - /usr/local/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.11.0 => 16.11.0 react-native: 0.62.0 => 0.62.0 npmGlobalPackages: react-na
Latest react-native app doesn't work ":CFBundleIdentifier", Does Not Exist
On OS X El Capitan v10.11.4 node --version v6.0.0 npm --v 3.8.8 react-native-cli: 0.2.0 react-native: 0.24.1 watchman --v 4.4.0 xcode 7.3 $ react-native init AwesomeProject $ cd AwesomeProject $ react-native run-ios [code block]
[FlatList] Rows aren't rendered until scroll
Hi, I have list view which displays partially local and partially remote data. Local data are initial for ListView.DataSource. This datasource is set in state of my custom component which wraps ListView and passed in render method to ListView. When are remote data received, new datasource is cloned by cloneWithRowsAndSections method and set to state of custom component. Problem is that are re-rendered only already displayed rows and new rows are rendered after scroll. Is it bug or how I should to force rendering of ListView? With react-native 0.5 it worked but after upgrade to 0.6 it behaves as described above.
NullPointerException:tempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)'
Is this a bug report? yes Have you read the Contributing Guidelines? yes, I am sorry that I cant offer more information about this exception except for this stack trace because the crash report was collected from google analytics, I have no idea to reappear this exception. Environment Environment: OS: macOS Sierra 10.12.6 Node: 8.4.0 Yarn: 0.27.5 npm: 5.4.0 Android Studio: 3.0 Packages: (wanted => installed) react-native: 0.51.0 => 0.51.0 react: 16.0.0-alpha.12 => 16.0.0-alpha.12 Target Platform: Android (7.1.1) mobile:MIX 2 android:7.1.1 java.lang.NullPointerException: tempt to invoke virtual method 'android.graphics.drawable.Drawable android.graphics.drawable.Drawable$ConstantState.newDrawable(android.content.res.Resources)' on a null object reference at android.graphics.drawable.DrawableContainer$DrawableContainerState.getChild(DrawableContainer.java:888) at android.graphics.drawable.DrawableContainer.selectDrawable(DrawableContainer.java:466) at android.graphics.drawable.StateListDrawable.onStateChange(StateListDrawable.java:104) at android.graphics.drawable.Drawable.setState(Drawable.java:735) at android.graphics.drawable.DrawableWrapper.onStateChange(DrawableWrapper.java:331) at android.graphics.drawable.Drawable.setState(Drawable.java:735) at android.graphics.drawable.LayerDrawable.onStateChange(LayerDrawable.java:1488) at android.graphics.drawable.Drawable.setState(Drawable.java:735) at android.view.View.drawableS
May 2024 iOS privacy manifest requirements tracking issue
UPDATE We now have guide on how to add a privacy manifest via your app config (app.json / app.config.js). --- Overview Recently, Apple announced that, starting May 1, they would start enforcing that all new apps and updates must declare approved reasons for using specific APIs in a privacy manifest, preventing uploads to TestFlight if the requirement is not met. These requirements also apply to 3rd party SDK's, with specific SDK's identified by Apple requiring a signature in addition to the manifest. If you submitted to TestFlight after March 13th, you may have received an email from Apple with an "ITMS-91053" warning, indicating that they found API usage matching an `NSPrivacyAccessedAPI` category in your app that will require these changes in order to meet the requirements after May 1st (common categories might include `NSPrivacyAccessedAPICategoryDiskSpace` and `NSPrivacyAccessedAPICategoryFileTimestamp`). What Expo is doing about it Expo engineers are actively engaged with this issue, doing everything in our power ensure that your app submissions continue uninterrupted despite the relatively short notice: - Adding privacy manifests to all affected modules maintained by Expo - Tracking progress on key dependencies not maintained by Expo (e.g., this PR to add the manifest to `react-native`) and ensuring our version validation is updated accordingly as these updates go live. - Providing guidance on how to add the privacy manifest to community-maintained modules - Prov
App Crash on Android OS 6 Samsung Galaxy S7 SM-G930FD (JSC Crash) 64 bit support A/libc: Fatal signal 11 (SIGSEGV)
Bug Report Crashed on launch Crashed with only this error log traced on android logcat A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 20217. To Reproduce react-native run-android and navigate to second screen from initial route through stack navigator. I am using `React-Navigation 3.6` App crashes as soon as I start going into `react-navigation` and crashing in `Samsung S7 64 bit CPU` device, working fine in other android devices which I am using. Expected Behavior just to work in a stable manner. like in earlier react-native version 0.58 Environment React Native Environment Info: System: OS: Mac OS mojave 10.14 Binaries: npm: 6.4.1 Android Studio: Version 3.2.1 Android 6.0.1 (real device: Samsung S7 SM-G930FD) React Native v0.59.3 Temporary Workaround: When I removed 64 bit ndk filters "arm64-v8a", "x86_64" from ndk abiFilters in defaultConfig block of buidl.gradle by provide only 32 bit support. It works fine. [code block]
couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found
App crash on Android integration with existing apps. Crash log. [code block] React Native version: System: OS: macOS 10.14.5 CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz Memory: 1.19 GB / 16.00 GB Shell: 5.3 - /bin/zsh Binaries: Node: 12.5.0 - /usr/local/bin/node Yarn: 1.16.0 - /usr/local/bin/yarn npm: 6.9.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: Android SDK: API Levels: 21, 22, 23, 24, 25, 26, 27, 28, 29 Build Tools: 23.0.1, 25.0.2, 26.0.2, 27.0.3, 28.0.0, 28.0.3, 29.0.0, 29.0.0 System Images: android-22 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom IDEs: Android Studio: 3.4 AI-183.6156.11.34.5522156 Xcode: /undefined - /usr/bin/xcodebuild npmPackages: react: 16.8.6 => 16.8.6 react-native: ^0.60.0 => 0.60.0 npmGlobalPackages: react-native-cli: 2.0.1 Steps To Reproduce 1. Create a new Android app which uses AndroidX. 2. Add react-native to Android application as, implementation 'com.facebook.react:react-native:+' 3. Run app on any android device/emulator. Sample project on GitHub which reproduces crash.
Missing request token for request: <NSURLRequest: 0x60000253e5a0> { URL: file://
Description I just upgraded to RN 0.63.0 and all fine, but only for upload using axios, i get [code block] React Native version: System: OS: macOS 10.15.5 CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz Memory: 163.19 MB / 8.00 GB Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.16.1 - /usr/local/bin/node Yarn: 1.22.4 - /usr/local/bin/yarn npm: 6.13.4 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.9.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2 Android SDK: API Levels: 22, 23, 25, 26, 27, 28, 29 Build Tools: 23.0.3, 27.0.3, 28.0.3, 29.0.0, 29.0.2 System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-R | Google APIs Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 4.0 AI-193.6911.18.40.6514223 Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild Languages: Java: 1.8.0_221 - /usr/bin/javac Python: 2.7.16 - /usr/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.63.0 => 0.63.0 npmGlobalPackages: react-native: Not Found Steps To Reproduce Here is my code snippet and that gives me error [code block] Expected Results Should upload file, it was fine in 0.62.2