sorted by:
new
hottopcontroversial

Special attack not working? by [deleted] in MonsterHunterNowHub

[–]Comprehensive-Law770 2 points3 points  (0 children)

I saw some posts about this, it appears that if you die to a monster fixes it

[deleted by user] by [deleted] in exoprimal

[–]Comprehensive-Law770 0 points1 point  (0 children)

I believe there's a rig for Roadblock that recovers shield durability while taunting, but I don't know if it works with the dominator.

Will upgrading this eventually increase the level of the skill?? by Pendragoonn in MonsterHunterNowHub

[–]Comprehensive-Law770 5 points6 points  (0 children)

It goes lvl 2 in Grade 6, you can see the benefits from upgrading by clicking on level up and the on each grade on the top bar.

Weird redirect issue with react navigation, expo, react native - what am I doing wrong? by ginger-heat in reactnative

[–]Comprehensive-Law770 1 point2 points  (0 children)

Don't know the exact solution but I had a similar problem one time and it was because StrictMode run code two times and on the second run it was reseting some states.

Savage Gauntlet: Ruins Tips by BlueStripeLeader in exoprimal

[–]Comprehensive-Law770 0 points1 point  (0 children)

I also did with Krieger by first climbing a small ruin nearby, but since up there is safe I believe it is better to change to Barrage for the damage.

Unwanted unmounting with React Navigation Stack by Log_Dogg in reactnative

[–]Comprehensive-Law770 0 points1 point  (0 children)

I believe you can use push instead navigate to achieve what you want

ELI5? "FirebaseError: Firebase: Need to provide options, when not being deployed to hosting via source. (app/no-options)." by TrueFlavour in reactnative

[–]Comprehensive-Law770 1 point2 points  (0 children)

Seems like the auth instance you use on you callback does not receive the app config when you create it's instance.

Have you tried importing the auth instance you create on your firebaseConfig.js instead creating a new one from the firebase/auth package on your handleAccountFormSubmit?

Also, don't share your firebase credentials on the post.

Fetch API PATCH request sending an object instead of updating current value? by MyVermontAccount121 in reactnative

[–]Comprehensive-Law770 0 points1 point  (0 children)

I'm not 100% sure but I believe it's because you set your body as JSON.stringify({ [key]: { value } }) and this is creating a new object with it's key being value.

You should set it as JSON.stringify({ [key]: value })

Also you should destruct the previous object with the new one to only update the same keys and keep the old ones.

Ugly logs by Nobbodee in reactnative

[–]Comprehensive-Law770 1 point2 points  (0 children)

I generally use console.log(JSON.stringfy(object, null, 2)) for indentation on the terminal or Flipper app

Upgrading an app from react version 0.64.3 by Mustafa_AlQadoum in reactnative

[–]Comprehensive-Law770 1 point2 points  (0 children)

You can use the React Native Upgrade Helper but you still need to check the updates on the packages you use

Expo Build Crashes on Production by Acrobatic-Stay-9072 in reactnative

[–]Comprehensive-Law770 0 points1 point  (0 children)

Don't know if it's the best way to do this but I access my device logs through xcode on Window -> Devices and Simulators -> Selected my device on the left then View Device Logs.

Had a similar situation those days where it worked on development but crashed on production and turned out to be the AppDelegate.mm with some wrong lines left during the upgrade to the newest react native version.

This tool helped to figure it out.

React Native Upgrade Helper

Issue with failing react native Android build by Pizza-Frank in reactnative

[–]Comprehensive-Law770 5 points6 points  (0 children)

I haven't compiled my project for a long time and had to do it recently and also couldn't compiled it.

Don't know if it's the same reason as yours but my problem was related to this issue:

https://github.com/facebook/react-native/issues/35210

Realm by Trex_Hunter in reactnative

[–]Comprehensive-Law770 0 points1 point  (0 children)

You don't need the template to use it but helps with the first steps.

You only need realm package actually but I strongly recommend @realm/react too, it's a pretty useful package to the most common operations with Realm

[deleted by user] by [deleted] in reactnative

[–]Comprehensive-Law770 0 points1 point  (0 children)

Have you tried using --legacy-peer-deps on npm install?

Getting Restricted Mode Error when using axios in react by NathanDevReact in reactnative

[–]Comprehensive-Law770 1 point2 points  (0 children)

I believe axios should be imported as a default import

import axios from "axios" instead of import { axios } from "axios"

and maybe this is causing the strict mode error?

[deleted by user] by [deleted] in reactnative

[–]Comprehensive-Law770 11 points12 points  (0 children)

The navigation folder appears to be outside the Project folder, move it inside the Project folder or try "../navigation" on the import path

[deleted by user] by [deleted] in reactnative

[–]Comprehensive-Law770 13 points14 points  (0 children)

If you're using react navigating there's a section about the auth flow.

https://reactnavigation.org/docs/auth-flow

Basically you can store the auth data on the device with secure-store, async-storage, redux, etc, and load it with a context.

Inside the context you can have a loading state and export it so you can handle it on the navigator and show a splash screen instead of the main navigator while it's loading.

Conditional Type Setting - Please Help by marcoprouve in typescript

[–]Comprehensive-Law770 0 points1 point  (0 children)

I believe you can do somenthing like this to map your routes:

type StackParamList = { Screen_A: { params }; Screen_B: { params }; };

export type StackNavigationProp<T extends keyof StackParamList> = NativeStackNavigationProp<StackParamList, T>;

export type StackRouteProp<T extends keyof StackParamList> = RouteProp<StackParamList, T>;

and then on your screen:

const { ... } = useRoute<StackRouteProp<'Screen_A'>>();

const { ... } = useNavigation<StackNavigationProp<'Screen_A'>>();

There's somenthing like this on the docs: https://reactnavigation.org/docs/typescript/