šŸ Sign in with Apple - New Plugin from Zeroqode

Hello, @haddad.anthony26
Thanks for your question.

In case you want just to store the name of the user in your database, you should ā€œCreate a new thingā€:
image

In case you are meaning something else - let us know.

Best regards,
Zeroqode Support Team

Hello, @jdubbya
We are sorry for your experience with this plugin and for the time, you spent configuring it :pray:

Allow us to note that this plugin is used by many users, and even though there are some difficulties in setting it up, the plugin works correctly. Our team is always ready to help with it since users’ experience is important to us.
That’s why we configured the plugin within your application and tested it numerous times.

Let us highlight that provided video was recorded yesterday, so our steps were the next:

  • We deleted your application from our Apple Console and entered your application for the first time;
  • We successfully signed in it the application, the data was recorded in the DB and server logs: Screenshot by Lightshot
  • Moreover, on the recorded loom you can find the user was logged in. We were able not only to log into our new account, but we were also able to fill out the information and choose a role: Screenshot by Lightshot
  • Here we can see that setup is complete Screenshot by Lightshot we believe that this process could not have been completed if the user had not been logged into the application.
  • After it, we decided to Logout from the app and Logged in one more time. It was successful too.

@jdubbya we should note that all these actions were not done through the database (run as) but from the front end of your application using the data from our apple account. Taking into consideration all of this, we are pretty confused that it is not working for you.

In order to resolve it, can you please provide us access to your application once again and we will totally test it from the beginning?

We are really interested in helping you.
Best regards,
Zeroqode Support Team

Finally figured this out - the login process fails silently when the user is logged into either Chrome or Edge, even if it’s using the same email address. Safari works fine, though, even if the user account addresses are different. Thanks for the persistence, I wouldn’t have tried again if not for your insistence. Probably you should update the documentation to include this caveat about browsers, or update the plugin to catch and log the error? I’m surprised I’m the first person to run across this.

Hello, @jdubbya
We are glad to hear that you was able to find the solution for your case.

Indeed, we have never encountered this behavior earlier, and never received requests from our users.

During the testing of your application, we used the Chrome browser, and moreover, we are always logged in to the browser with our work accounts.
Right now, some of our colleagues tested your application ( they were logged in the Chrome browser) and everything is working properly:

Can you please let us know if someone from your colleagues is facing the same issue?
It is possible that the issue is related only to your device\cache\cookies.

We will be glad to help you with anything else and improve your experience with the plugin and improve the rating.

Looking to hearing from you soon.
Best regards,
Zeroqode Support Team

Yes, same problem across 2 PCs and 1 Macbook, only in Chrome and Edge, not in Safari

Hello, @jdubbya
Thanks for this clarification :pray:

We discussed internally this behavior and have an assumption regarding the root cause.
It is possible that some of the extensions, you are using within your Chrome\Edge browsers affect on the plugin.

Please allow us to highlight once again, that we have never encountered this problem and have not received any such requests from users.
Therefore, we conclude that it is related to your device or browser specifically.

Perhaps your company uses some specific extension that affects the operation of the plugin in this way.

Please disconnect your extensions and try once again :pray:

We are looking to hearing from you soon.
Best regards,
Zeroqode Support Team

It’s not just my machine - it’s my PC, plus my partner’s PC and his Mac book, and they all have the same issue. We do have some extensions in common on our PCs in Chrome, though not in Edge.
And he has no extensions on Chrome on his Mac. So it’s still a mystery. But I’m not going to sink any more time into this, I’ll just make a note that the user must log out of their browser session before using the Apple login. Not the best solution but better than nothing.

Hi @ZeroqodeSupport

I’ve used to have the sign in with apple working well. Now I always get invalid redirect url.

Could you please have a look at my app?. You should have edit rights.

Thank you

Hello, @haddad.anthony26
We are sorry to hear about it.

It could be possible in case you changed some links within your Apple Console or Backend Workflows.
We still have an access to your application, however, the process of signing in was changed.

Was noticed that the button is not displayed when we try to log in to the app:
https://www.loom.com/share/9d6ca06997874af88df45d07503ee822

Note that this button should be always visible on the page :pray:
Thus, during the Sign Up process, we were unable to check the button performance.

Can you please provide us the video reproducing this error and including each of the required steps?
It will help us to investigate your issue.

Best regards,
Zeroqode Support Team

It would be easier that you make it visible to reproduce the error instead of me living a buggy button on my live version.

And we try to replicate the behavior in live conditions so would be better don’t you think?

Can you please let me know what should be fixed?

Thanks,

Hello, @haddad.anthony26

We need to note that our team is not able to make any changes to the Version-Live of your application. Moreover, we can’t make changes to your version-test of an app and deploy it further.
As it was noted, your button was not visible even on the version test, but this is related to the Responsive Design of your application. So, you just need to place the button in a way it will not be collapsed by other elements and groups.
We changed a bit the placement of the element in order to test it.

But allow us to note that the issue is related to the link in your Apple Dev. Console, since it seems like you changed the link there.
Please share the screenshots of the redirect URLs from your Apple Console, so we will define exactly what was changed.

Also, we need to note that immediately after we accessed your application on the version-live, it was proposed to download your native application. We did it, however, there is no Sign In with Apple Button in your application. Unfortunately, we can’t fix this within your native application (since it is wrapped with a third-party service).

Looking to hearing from you soon.
Best regards,
Zeroqode Support Team

Thank you for the answer.

The sign in with apple element is now visible on the live version and leading to invalid request url.
Bliss Coach >> Get started > Profile in the menu >> sign in with apple

I didn’t change anything in the Apple Dev. Console. here is a screenshot of it.

I need to solve this asap, your help is much appreciated.

Thank you

Hello, @haddad.anthony26
Thanks for the screenshots.

Your issue is related to the fact that currently, you have another, custom domain, but not the default one, provided by the Bubble Platform.
All your Redirect URLs and even Domain is linked with your ā€œoldā€ application. Thus, now, the plugin just couldn’t find the mentioned application.

Please use this domain name:

For the Redirect URLs, you should create the links in the same way:
https://blisscoach.app/version-test/api/1.1/wf/applesignin
And other links (for version live and initialization) should be created, using this one.

Please redo it and let us know, so we will be able to continue our investigation.

Best regards,
Zeroqode Support Team

this is done but still doest work.

Find here my records and redirect.


Thank you for your help

@haddad.anthony26

Please note that you should not only change the links but Initialize the plugin from the beginning. Ths, we asked you to let us know when all the links would be changed.

The redirect URLs should be changed in your Apple Console, not only for the buttons.

You should remove the old domain and use only the current one: https://blisscoach.app/
Also, all your redirect URLs here should be removed and added with a new domain: https://blisscoach.app/version-test/api/1.1/wf/applesignin , the next one should be with the initialize path and one more - for the version live.

Please change the links in your Apple Dev. Console and let us know about it.
Best regards,
Zeroqode Support Team




Done all your actions but still doesn’t seem to work.

@haddad.anthony26

It seems like there are some issues with the links in your Apple Dev. Console. Thus, we kindly ask you to provide us access to your Apple Console (share with us your credentials in DM). Also, please note that you will receive a TFA code on your phone, so you need to share it immediately with us.

It will help us to speed up the process.

We are looking to hearing from you soon.
Best regards,
Zeroqode Support Team

Hello
Apple sign in takes up to 20" to get back to the app and finalize the login process. Which is acceptable on a browser (you actually see that something is happening), but on a native app the impression is, that something is wrong. What is the best approach to overcome this extremely long wait? Considering that the (empty) page shown is Apples…

Totally agree… @ZeroqodeSupport

It is not usable by any app - we don’t even control the look of the loading page as it is result in a white blank page from Apple

There is no point for the moment to use Sign with Apple if on mobile the experience is not possible… We’re probably a lot having to face this.

Since Apple will not accept your native app without it, you’re forced to use it…

1 Like