Thomas Leing

Hello, thank you for reaching out -- we generally advise using the [Amplify docs](https://docs.amplify.aws/start/getting-started/installation/q/integration/android/#option-2-follow-the-instructions) instead of the AWS tutorial you linked to because it's out of date, but it seems...

Just FYI, the GitHub build is failing because you're using a more recent build of one of the packages (`prism` from 1.2.3 to 1.2.6) based off of your `yarn.lock`. I...

> > Just FYI, the GitHub build is failing because you're using a more recent build of one of the packages (`prism` from 1.2.3 to 1.2.6) based off of your...

~~also looks like the build is failing on GH with this error:~~ resolved!

if you select RN as an integration on `/start` it still sets your filterKeys platform to `js` (image below) so if you then pick `/lib` it redirects to JS instead...

@umerk44 Judging based on the error messages (`npm ERR!: ... routines:ssl3_get_key_exchange:bad signature`), it seems like that may be an issue with your installation of NPM and nothing to do with...

Closing this issue, please let us know if you have further questions by opening a new issue.

Thanks for reaching out, @nzayatz14! It seems like this may happen when the library is unable to construct a notification channel -- you may want to look for Logcat messages...

@nzayatz14 ah yes, Pinpoint creates (or reuses) a notification channel whenever it receives a notification -- it should show up as "Notifications" in the device settings. Please try using that...

@nzayatz14 in almost all cases I believe you'd want to create the `NotificationChannel` yourself with a channel ID matching the one that Pinpoint is looking for, `"PINPOINT.NOTIFICATION"`. Then, instead of...