You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2022. It is now read-only.
Hi
V5 is alpha and has its own hooks. This project is temporary and for v3 or
v4 only.
What do you want to modify in the doc? Can you submit a PR?
Le dim. 5 janv. 2020 à 15:37, Dimitri KOPRIWA <notifications@github.com> a
écrit :
Using ***@***.*** seems to fix the issue, this should be
updated in expo doc
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#57?email_source=notifications&email_token=AAFW6PXWNYZHE6MGLSIKBZ3Q4HWENA5CNFSM4KC3QLSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDYKAY#issuecomment-570918147>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFW6PWH55IQX64QGFCFSDLQ4HWENANCNFSM4KC3QLSA>
.
I have created the following issue regarding
useNavigation
error : https://github.com/react-navigation/native/issues/37Should I instead use this module? If yes, I am currently implementing react-navigation 4.0.10, while you seems to support 3.11.1 (See https://github.com/react-navigation/hooks/blob/master/package.json#L62)
Which packages should I use to access the
navigation
object?The text was updated successfully, but these errors were encountered: