[docs] Fix inconsistent terms usage, ellipses usage and update vale's token ignore scopes (#24593)
[docs] Fix vale warning about Latin abbrv., inconsistent case in headings and update verbiage (#24452)Co-authored-by: Bartosz Kaszubowski <[email protected]>
[docs] Fix broken links as reported after audit (#24397)Co-authored-by: Bartosz Kaszubowski <[email protected]>
[docs] Fix push-notifications-setup.mdx formatting (#24407)
[docs] Fix incorrect platform order and latin abbreviation usage warnings from Vale (#24338)
[docs] Fix Bracket Typo in Push Notifications Guide (#23934)
[docs] Update push notifications setup guide to use development builds (#23736)
[docs][notifications] ack FCM legacy key deprecation (#23489)# Why Folks are asking about this a lot. We should acknowledge the key is deprecated and that there's a deadline, so users know we're
[docs][notifications] ack FCM legacy key deprecation (#23489)# Why Folks are asking about this a lot. We should acknowledge the key is deprecated and that there's a deadline, so users know we're aware of it and that we will communicate more about it in the future. Google's messaging here is prompting some to actually try to input the v1 key into Expo's app credentials, which doesn't work. <img width="912" alt="image" src="https://github.com/expo/expo/assets/8053974/9808e992-0765-4d80-92ce-ac0537da9432"> Also, removed the "legacy application identifier" notes, since that leads to a lot of "legacy" talk, referring to two totally different things, in a rather tight space. I don't recall "legacy application identifier" terminology being used in many other places, and I think that all is pretty far in the rear-view mirror, so maybe not needed? If we do keep something about it, I think it should be just advice to use `expo push:android:clear`. I don't think there's a reason to update credentials in the global CLI at this point. # How Updated docs # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Aman Mittal <[email protected]>
show more ...
[docs] Update example in sending-notifications.mdx (#23270)
[docs] Fix Apple's request push address for custom push notification (#23162)
[docs] fix Terminal content layout shift, remove unused page imports (#22596)
[docs] Fix internal links to avoid redirects (#22498)
[docs] Add redirects for sections that can be referred as short urls (#22222)
[docs] remove EAS Notify mention from notifications FAQ (#21899)
[docs] PushNotifications: fix sentence (#21698)
[docs] PushNotifications: fix heading name (#21700)
[docs] Update Symfony notifications library
[docs] Set correct `code` data type for ticket response in notification guides (#20835)
[docs] Minor fixes for push notifications and API references (#20901)
[docs] Update Push notifications and expo-notifications docs (#20270)Co-authored-by: Jon Samp <[email protected]>
[docs] FCM-specific advice for InvalidCredentials error (#20691)# Why The `InvalidCredentials` error can happen for FCM/ Android, as well, but we only had iOS-specific advice, which also previo
[docs] FCM-specific advice for InvalidCredentials error (#20691)# Why The `InvalidCredentials` error can happen for FCM/ Android, as well, but we only had iOS-specific advice, which also previously referenced Classic build commands. # How With FCM, `InvalidCredentials` can be returned on a push receipt [due to a 401 from the FCM endpoints](https://github.com/expo/universe/blob/main/server/push-hydrant/src/fcm/FcmSend.ts#L86), which [seems to be associated with passing an incorrect server key](https://stackoverflow.com/questions/37633188/firebase-401-unauthorized-error-fcm), which we address in our setup instructions, so the the troubleshooting advice links back to that. Would welcome any additional suggestions for Android/ FCM troubleshooting. # Test Plan <img width="823" alt="image" src="https://user-images.githubusercontent.com/8053974/210407280-e7324fd0-87ce-4e9c-bcf4-6cb4a3210276.png"> Co-authored-by: Aman Mittal <[email protected]>
[docs][packages] fix problematic Apple links (#20591)
[docs] old text and lists components removal (#20442)
docs updates (#20403)# Why - Update a bit of the language across the docs in regards to Expo Go. - Clarify that Expo Go is not meant for production app development or previewing apps.
[docs] Sending Notifications: list library for Laravel (#20099)
12345