When I refer to the Google RTDN documentation to do the relevant setup, I encountered a problem when proceeding to the second step. Immediately after I selected the preset theme, an error message appeared in the web page's console, at which point the Connect to Google button remained disabled, and I'll post an image of the error below. Of course, I'm sure that each step has been set up correctly according to the documentation. all But I didn't find any answers about it in search engines and community, so any help there?
I encountered the same issue. I replaced the Google Services JSON and changed the Cloud Console, but the Connect to Google button was not active. What could be the reason?
When I refer to the Google RTDN documentation to do the relevant setup, I encountered a problem when proceeding to the second step. Immediately after I selected the preset theme, an error message appeared in the web page's console, at which point the Connect to Google button remained disabled, and I'll post an image of the error below. Of course, I'm sure that each step has been set up correctly according to the documentation. all But I didn't find any answers about it in search engines and community, so any help there?
Hey! I have the exact same issue and I can’t move forward. Did you find a solution?
@angel1996 @cesapptech Finally someone has seen this problem with me, I double checked my settings twice following the documentation and the problem still existed when I proceeded to this point. I haven't solved the problem yet and haven't searched for useful information, so I'm looking forward to an official reply!
Hi @fainso-3fccfc @cesapptech @angel1996 @justin-7c8368 thank you for reporting this. Can you confirm that you have all made sure that you have enabled PubSub for your projects, see our docs here? Once you have done so you should be able to select a topic id and connect to Google, and we recommend using Google Chrome as it works best with our dashboard. If this still doesn’t work please let me know.
I’ve actually just figured out a way around the issue. It looks like having RevenueCat generate the notifications topic ID for me wasn’t working. By going into the pub/sub configuration in the Cloud console, I was able to create a topic ID manually. Once I had the topic ID created, I was able to go back to RevenueCat and select the topic from the dropdown. After that the connection seemed to work as expected.
Yes, I am certain that I enabled PubSub according to the link in the documentation and followed the steps. Perhaps it is a misunderstanding, but it could also be a bug.
By the way, I am indeed using Google Chrome.
Finally, following @justin-7c8368 solution, I was able to successfully connect to Google and ensure that I could continue working. This is a great solution.
I’ve actually just figured out a way around the issue. It looks like having RevenueCat generate the notifications topic ID for me wasn’t working. By going into the pub/sub configuration in the Cloud console, I was able to create a topic ID manually. Once I had the topic ID created, I was able to go back to RevenueCat and select the topic from the dropdown. After that the connection seemed to work as expected.
Hi @fainso-3fccfc @cesapptech @angel1996 @justin-7c8368 thank you for reporting this. Can you confirm that you have all made sure that you have enabled PubSub for your projects, see our docs here? Once you have done so you should be able to select a topic id and connect to Google, and we recommend using Google Chrome as it works best with our dashboard. If this still doesn’t work please let me know.
Hi Haley, its worked thank you.
When I refer to the Google RTDN documentation to do the relevant setup, I encountered a problem when proceeding to the second step. Immediately after I selected the preset theme, an error message appeared in the web page's console, at which point the Connect to Google button remained disabled, and I'll post an image of the error below. Of course, I'm sure that each step has been set up correctly according to the documentation. all But I didn't find any answers about it in search engines and community, so any help there?
Page 1 / 1
I encountered the same issue. I replaced the Google Services JSON and changed the Cloud Console, but the Connect to Google button was not active. What could be the reason?
fainso-3fccfc wrote:
When I refer to the Google RTDN documentation to do the relevant setup, I encountered a problem when proceeding to the second step. Immediately after I selected the preset theme, an error message appeared in the web page's console, at which point the Connect to Google button remained disabled, and I'll post an image of the error below. Of course, I'm sure that each step has been set up correctly according to the documentation. all But I didn't find any answers about it in search engines and community, so any help there?
Hey! I have the exact same issue and I can’t move forward. Did you find a solution?
Thanks a lot in advance :)
@angel1996 @cesapptech Finally someone has seen this problem with me, I double checked my settings twice following the documentation and the problem still existed when I proceeded to this point. I haven't solved the problem yet and haven't searched for useful information, so I'm looking forward to an official reply!
I am also having the same issue. I’ve regenerated and re-uploaded credentials and double checked all of my configuration to no avail.
Hi @fainso-3fccfc @cesapptech @angel1996 @justin-7c8368 thank you for reporting this. Can you confirm that you have all made sure that you have enabled PubSub for your projects, see our docs here? Once you have done so you should be able to select a topic id and connect to Google, and we recommend using Google Chrome as it works best with our dashboard. If this still doesn’t work please let me know.
I’ve actually just figured out a way around the issue. It looks like having RevenueCat generate the notifications topic ID for me wasn’t working. By going into the pub/sub configuration in the Cloud console, I was able to create a topic ID manually. Once I had the topic ID created, I was able to go back to RevenueCat and select the topic from the dropdown. After that the connection seemed to work as expected.
Yes, I am certain that I enabled PubSub according to the link in the documentation and followed the steps. Perhaps it is a misunderstanding, but it could also be a bug.
By the way, I am indeed using Google Chrome.
Finally, following @justin-7c8368 solution, I was able to successfully connect to Google and ensure that I could continue working. This is a great solution.
I’ve actually just figured out a way around the issue. It looks like having RevenueCat generate the notifications topic ID for me wasn’t working. By going into the pub/sub configuration in the Cloud console, I was able to create a topic ID manually. Once I had the topic ID created, I was able to go back to RevenueCat and select the topic from the dropdown. After that the connection seemed to work as expected.
Hi @fainso-3fccfc @cesapptech @angel1996 @justin-7c8368 thank you for reporting this. Can you confirm that you have all made sure that you have enabled PubSub for your projects, see our docs here? Once you have done so you should be able to select a topic id and connect to Google, and we recommend using Google Chrome as it works best with our dashboard. If this still doesn’t work please let me know.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
