Tag Info

If you're facing this Android 16KB page size Play Store rejection with React Native, there's a detailed step-by-step fix guide available here: https://community.7edge.com/t/react-native-android-16-kb-...

I got the solution! Use React Native Camera Kit Library.... This library is working fine.

Ok, after many hours of searching, all I had to do was Edit my push-notification-service.ts like: import { useState, useEffect, useRef } from 'react'; import { Text, View, Button, Platform } from '...

You’re getting this error because react-native-keychain isn’t available in Expo Go, so Keychain is coming back as null. That’s why it crashes on: Keychain.setGenericPassword(...) It’s not your token, ...

I've created a small Expo / EAS plugin that handles the change persistently and without the need for XCode: https://github.com/vaiden/expo-eas-ipad-support

This error is happening because you are calling setNotificationChannelAsync to "vendas", but for it to properly communicate, you need to set it to default value. Here is an example from the ...

Issue was due to stale React Native autolinking cache where react-native-keychain was missing from android/app/build/generated/autolinking/.../PackageList.java; I verified it via grep, cleared android/...

If you just need to inspect/debug a JWT quickly without writing code, you can use apidevtools.dev/tools/jwt-decoder — it decodes the header, payload, and checks expiry directly in the browser, no ...

Can you add the following permissions as well? This audio permission just to be sure. android.permission.MODIFY_AUDIO_SETTINGS And if you are using Android 11+ you will also need the following ...

Thanks for the suggestion, Shaun Husain

React Native is really meant to allow you to write general purpose (form/text driven layouts) that map into using native controls on a target mobile platform, so think sort of just wrong tool for the ...

I agree, many times, just AI alone will cause huge issues for you in the future (like what to do if the app crashes, the AI crashes, etc.), and also, many times it messes up, and I had to manually fix ...

My tip- learn to program. Actually program. If you can't do that, even if you get AI to spit out something useful (doubtful), you'll have a buggy, non-performant, insecure piece of junk that will ...

I tried most of the solutions here and even ask claude opus 4.6, none works for me. What fixed it for me was removing lineHeight from Text

However, it a very late response but perhaps you need to improve the code for logging. It should be something like below. appCheck .initializeAppCheck({ provider: rnfbProvider, ...

Why is this an advise question instead of a normal question?

Was this generated by AI? It seems to be the case.

To answer your question: Q1: What exactly triggers this SDK version warning? Is it strictly tied to my installed Xcode version? A1: The OmronConnectivityLibrary I suspect it may cause the warning, you ...

This message can also appear if the build you're trying to run didn't have the device you're trying to run it on in the provisioning profile. (Solution - new build after adding the device to the ...

Fabien Lenoir's comment worked for me: For me, there was an override of the react-devtools-core version. I removed it, and the error went away. Just remove react-devtools-core in package.json.

useSafeAreaFrame - could provide you modal size import {useSafeAreaFrame} from 'react-native-safe-area-context' const frame:Rect = useSafeAreaFrame() export interface Rect { x: number; y: number;...

Did you try try { /// Update the iOS foreground notification presentation options to allow /// heads up notifications. await FirebaseMessaging.instance ....

You can disable it programmatically at app startup by calling the native DevMenuPreferences module: // app/_layout.tsx (or your root file) import { requireOptionalNativeModule } from 'expo'; const ...

I found out what it is, https://expo.dev/blog/expo-router-v55-more-native-navigation-more-powerful-web#toolbars. It's not the actual menu, it's a Toolbar, so it is something entirely different than ...

Switching to react-native-video resolved this issue for me

Yes indeed, I was thinking the same thing. But how I use it now with the NativeTabs, more requires an actual route. So I did what you said, using the route more.tsx but this actually re-routes you (...

The way I would do something like this is to make the more button trigger a Modal to open via a function, and the Modal has the options. You can set the modal styling however you want, such as clear ...

Once a channel is created, its sound cannot be changed. Android caches the channel settings permanently unless the channel is deleted or the app is reinstalled. So uninstall the app from the device/...

Since React Native 0.77 mixBlendMode style property is supported.

Dumb Fix I had this occur to me on the following system (I'm aware this post is for another version, but its the only one I came across): Mac OS Tahoe 26.3.1 Xcode 26.3 My simulator was working ...

You can use other third party libraries or why not try not change native code in XML and swift? This will not take much effort.

Try the following Remove @react-native-async-storage/async-storage from your package.json Delete your node_modules & package-lock.json file Delete Pods folder & Podfile.lock in your ios ...

If you must go past that error and successfully invoke the function outside the client app, you must make a POST request to the url and pass a data field in the body which can have a JSON value. This ...

I was stuck with using KeyboardAvoidingView, this should be fixed from their end (react-native). The solution that ended up working for me was using ` react-native-keyboard-aware-scroll-view ` this ...

You have an undefined package, which tends to break commands like running the doctor up. Go into your package.json or package-lock.json (maybe even both), and remove this undefined definition. Next, ...

Your node_modules has react-native 0.68.2 installed but your package.json is asking for 0.84.1. Thats a massive version jump (0.68 is from like 2022) so npm cant resolve the peer deps because ...

The reason you’re seeing undefined is that React Native’s TextInput ref doesn’t expose a .value property. import React, { useRef, useState } from 'react'; import { TextInput } from 'react-native'; ...

In React Native, TextInput doesn't expose a .value property Use useState import { useState } from 'react' import { TextInput } from 'react-native' const MyComponent = () => { const [value, ...

If you are using WSL2, you should know it runs on a VM, so you need Windows to forward traffic from that port to it. Here's an updated answer (2026) with troubleshooting steps: https://stackoverflow....

You development server and your testing device should be on the same network. The easiest solution would be to use a tunnel: expo start --tunnel Alternatively, let's configure everything properly: ...

You are doing something wrong. I found the bug Since your export logic seems to rely on the actual names of the cities and pumps, the easiest way to fix this is to tell the Dropdown to use the label ...

Even I was using the custom development builld i was still. getting the issue then run this command npx expo prebuild --clean theeen run app again npx expo run:ios or andriod

Changes should be like this in AppDelegate.swift file override func bundleURL() -> URL? { #if DEBUG return RCTBundleURLProvider.sharedSettings().jsBundleURL(forBundleRoot: "index") #...

The code you posted needs to handle second factors in order to support the client trust feature, which is critical for preventing credential stuffing attacks. You could turn off this feature in your ...

This is NOT cache, NOT Node, NOT expo-av. This is a known conflict inside Expo. It’s a dependency alignment issue inside Expo native layer.

If you don't mean you want the text to appear in the same size as on your device, then I am not sure what exactly you would want to "calculate" here?

Thanks for your idea. I don't ask question like "handling font-size based on font-size". In mobile devices, we are able to change the font size just like display size ( standard/large/small)....

Your question about "handling font-size based on font-size" sounds as if you might think, the solution here was to recognize that the user configured their device to use a larger font size - ...

The behavior (bad quality on first launch, good after login/logout) suggests the video loads before the app/native layer is fully ready. When you log in and out, the Video component remounts and loads ...

This an old issue but knowing how painful it is to solve Amplify related issues, I'm sharing what worked for me. What worked for me was implementing a custom authSessionOpener to use expo-web-browser ...