There are some other things that have to be done from the Firebase side for the AppMySite build to be able to recognize that you turned on push notifications for the Firebase App.
Here’s a good walkthrough on it:
You have to make sure the APN’s Auth Key is created in your Apple Dev account and set as well as the Web Push Certificate
You have to go to Firebase Project > Project Settings > Cloud Messaging to make sure those are done first before you attempt to build.
Figured this out earlier today and wanted to make sure others were aware.
PLease, support team, update your instructions for setting up Firebase plain notifications to include more details around how to make this work for iOS and Android so that it is 100% clear to your users how to make this work. Many who use this platform may find the Firebase and other development environments unclear or opaque and your instructions are helpful, but not complete and the resulting error messages (e.g., when a build fails) are not detailed enough to understand what should be done to fix the issue.
Additionally, the instructions at the link above should be part of the step-by-step process in the interface of appmysite.com…where the user can access those steps directly through the interface…the walk-through would be so much more intuitive and helpful to avoid frustration and confusion around what is already convoluted process.
After seeing this post, and adding a “Key Pair” in the Cloud Messaging - Web Push certificates section of the Project dashboard, THEN regenerating the configuration .json file and uploading it in the Notification Build Settings, the build still fails.
More information and details are needed here. Please.
Thank you for sharing your detailed feedback regarding the setup of Firebase notifications and the challenges you encountered during the process. We deeply value your input as it helps us identify areas where we can improve and make our platform more user-friendly for everyone.
We understand that the current instructions for setting up Firebase notifications may not be as comprehensive or intuitive as they should be, especially for users who may find development environments like Firebase challenging. I want to assure you that we are actively working on making our Knowledge Base (KB) articles more detailed and straightforward.
In addition to this, we are reviewing how these instructions are integrated into our platform interface. Your suggestion to incorporate a step-by-step walkthrough directly within the platform is incredibly valuable, and we are exploring ways to implement this to make the process more intuitive and minimize potential confusion.
Regarding the issue you encountered with adding a “Key Pair” in the Cloud Messaging section and regenerating the configuration file, I’ve shared this specific feedback with our technical team. We are investigating how we can improve error messaging and provide clearer guidance when such issues arise.
Your feedback is critical in helping us refine the user experience, and we appreciate your patience as we work to address these concerns. If you need further assistance or encounter any roadblocks in the meantime, please don’t hesitate to reach out—we’re here to help.
…at the very bottom it says, "…If you only want to enable plain notifications, you’re not required to generate the SHA-1 key. "
Does this mean that if I’m only using Plain Notifications, that including the SHA-1 key in the configuration file (e.g., in the firebase settings) will cause the build to fail?
To clarify, the SHA-1 key is no longer a mandate for enabling push notifications on our platform. You can use plain notifications without needing to generate or include the SHA-1 key in your Firebase configuration file.
This has been thoroughly tested, and omitting the SHA-1 key will not cause the build to fail when configuring push notifications. If you encounter any issues or need further assistance, please don’t hesitate to reach out, and we’ll be happy to help.