🍏 Sign in with Apple - New Plugin from Zeroqode

[nedbrush]

Hi @Julia, I am having the same problems as @YuryNB. I have cases where the user gets logged in and I can see Current User information, but there is no user in my db. That’s a major problem.

I am also having the 400 error. In my version-test (ie unpublished version), I can create an account with sign-in with apple and the user can log out and log back in. It works. When I publish it, I change the URL redirect (to remove “version-test/” from the element and API workflow). Once published, the user can create an account, but they can’t log in.

Lastly, I’m having a third issue where the API workflow succeeds and sends me to the success page, but the user is still not logged in. I don’t see how I have control over this as the workflow should be signing up the user.

Honestly, this plug-in is not working well for me. This plug-in is required to use BDK to publish in the App Store using social logins. Until it’s working better, I, like @YuryNB, have no choice but to abandon social logins.

Here’s my page: https://app.besties.co/signin_landing_1

Thanks,
Ned

[YuryNB]

Hi @nedbrush

According to the problem with missing user in the database - check your success redirect url. It might be url of test version, so user will be created in the test database, even if you started from prod environment.

[nedbrush]

Thanks @YuryNB. I think my URL redirects are all correct, but I may have discovered the cause. I cleared my cache between “version-test” and released and it appears to behave correctly.

@Julia can you see if the browser cache could be the cause of the misbehaviors I was seeing (described earlier in the thread)?

Ned

[Julia]

Hi, guys!

@YuryNB apologies for the slow reply due to weekends. We were investigating your case to understand what was going wrong on your side as on our side it worked. That means that something is missing in the settings or the way they are set up. For now, we noticed that you have disabled some workflow and we cannot test it properly, unfortunately. I do understand that it is important for you and time is precious, and I’m doing my best to help you.
As now we unable to test the app properly (due to disabled workflows), could you please replicate the settings from the Live Demo (we have updated them a bit by adding an event in the frontend) and give it another try. It should help. Also here is an updated doc: https://docs.zeroqode.com/plugins/sign-in-with-apple-plugin.

In case, you still want a refund then, could you please apply directly to the bubble: https://bubble.io/contact , because all payments go through the bubble marketplace. I believe they can help you in this case.

@nedbrush as for the missing users, the @YuryNB gave a right direction, meaning to check if the database is “Live” as well as the app page.

So, the URL with the ID is stored in the browser history, it means that the clearing cash and cookies can really help. Anyway, I have checked your app and successfully signed in, signed out and signed in again in Live.

[fitnet]

Hi,

Great plugin! I am using this in my app.

I needed one help, I need to pass URL parameters in my app after the user sign up/ login. But if the user does this action using apple signing, I’m not able to retain URL parameters. Can you tell me a way I can do this?

Thanks,
Naman

[Julia]

Hi, @fitnet!

Thanks for reaching out!
You can pass URL parameters in my app after the user sign up/ login through the action “Go to page” when the page is load (see screenshot as a reference).

Hope this helps!
Best, Julia.

[Ecaterina]

Hello, @02hoya
Thanks for your question.

First of all, allow me to mention that the Red Field means that you have an error, that is demonstrated here:

Probably, you can detect the exact error by looking on your panel and completing this field correctly.

Please carefully follow instructions, especially the Plugin API Workflow section:

Sign-In with Apple Plugin

In case you cannot solve the issue by yourself, please provide us more detail about it.
Please provide us the screenshots of your workflow with current settings for all actions and we will check it.

Regards,

[02hoya]

Thanks Ecaterina, definitely know it is an error (I’ve been building in Bubble for a while)…
My question is around why the error is showing up. Again, I’ve followed all of the documentation / instructions extremely closely, including the Plugin API Workflow. Every time I try to include Response Code, Id Token, or User Data on the endpoint workflow, it throws an error and won’t allow for “Request Data’s Code” and other entries Zeroqode has in its documentation.

So I guess I’ll need to create a visual step-by-step pdf on my workflow and settings for you to check? I’ll put that together now, and email it. I appreciate the support on this, but honestly the documentation could be more clearly laid out.

[Ecaterina]

Hello, @02hoya

I’m afraid, we can not reproduce or investigate this issue without more info. Please attach all the necessary info like:

• error screenshots from debugger and browser console;
• the screenshots of your current settings;
• how to reproduce your issue;

This information will help us to investigate and resolve your case.
Looking to hear you soon.
Regards,

[Ecaterina]

Hello, @02hoya

By this message, I would like to notify you that we have checked your application and now all is working perfectly.

The issue was the next: on your page were places 2 Plugin elements and one of them you also started to set up, but the size of the button itself was the smallest, and it was not even visible on the page. Please find this screenshot:

Apple’s policy is quite strict and you can’t put two plugin elements (SignInWithApple) on the same page. What’s more, you can’t configure both of these items at once.

Once we removed this element - the missing steps for the correct work of the plugin were set automatically.

Hope this will help you to use your application with success.

If you like our plugin, could you please rate it by going to the Plugins tab in Bubble editor? You can find the plugin by name and give us as many stars as it deserves

The more feedback we get, the more motivated we to build great plugins

Thanks!

[02hoya]

Big thanks to Ecaterina and the team for all of the help on eventually resolving the issue I was having with the plugin. Really appreciate it!
A couple things for others to remember:

1. Make sure you copy exactly every Apply ID, key, etc that you get of the Apple Developer dashboard. Sometimes - especially when you enter the long authorization key - it does not copy exactly as when you download it from the Apple Dev site.
2. The plugin allows for a new user to sign in via their email, but you are not able to pull anything else - e.g. their name, picture, birthday, or any other piece of information. If anyone has found another way to do this via Apple signin, please let us know

Thanks again, Zeroqode support team!

[Ecaterina]

Hello, @02hoya
Glad to hear that I was helpful to you.

Also, thank you for describing the important points here. Please be free to contact us in case of necessity.
Additionally, we will be happy to receive your review on the Bubble ( please rate it by going to the Plugins tab in Bubble editor).

Thank you.
Best regards,

[jared]

I have the plugin working and it’s great! However, I am having many users create duplicate accounts because they don’t realize how Apple’s relay email address works and so they end up with two accounts, for example: customer@email.com AND randomcharacters@privaterelay.appleid.com.
On Apple’s dev documentation here

They list this:

Prevent Duplicate Accounts

A user may already have an account in your system, but may attempt to use Sign in with Apple to log in to that account. Sharing the real email address that’s associated with the user’s Apple ID may not help, because it may not be the same email used to create the account with your system. There are a couple of ways you can mitigate this issue:

• Implement the ASAuthorizationPasswordProvider class to detect and offer keychain credentials that the system already knows about. This works seamlessly to detect and use existing accounts, and prevents new accounts from being created using Sign in with Apple.
• For new accounts created using Sign in with Apple, let the user know that they’ve created a new account, and ask if they have any existing accounts to link to.

Is this possible with this plugin?

[jared]

Any ideas on this @Ecaterina?

[Ecaterina]

Hello, @jared
I’m sorry for my late reply.

Indeed, the issue with creating duplicate accounts by users exist.
For your case, allow me to recommend you to use the second solution, namely:

• For new accounts created using Sign in with Apple, let the user know that they’ve created a new account, and ask if they have any existing accounts to link to.

This feature is not presented in our " Sign in with Apple" plugin, but it is very simple to create it within your app by adding a PopUp. In this PopUp, you should ask users if they have any other account in Apple.

Please follow this link to create a PopUp: https://bubble.io/video-course/creating-a-popup-form-1604599371215x454769733916426200

As for the first proposed solution, namely: “Implement the ASAuthorizationPasswordProvider class to detect and offer keychain credentials that the system already knows about. This works seamlessly to detect and use existing accounts and prevents new accounts from being created using Sign in with Apple.” it is not available in our plugin, unfortunately.

We’ve taken into consideration the ability to add this in future updates. We need to see how feasible it is to implement.

Thanks for understanding and your feedback!
Best regards,

[kate]

Friends!

We have updated the Sign in with Apple plugin documentation
Hope you will find the new style of the doc helpful and more engaging:
Sign-In with Apple Plugin - Zeroqode Documentation

Regards,

[Ecaterina]

Hello, @jared

By this message, I would like to notify you that we have investigated the possibility to Implement the ASAuthorizationPasswordProvider class to detect and offer keychain credentials that the system already knows about within our plugin and this feature is impossible.

However, as a solution for preventing the creation of a duplicate account, you can use the Pop-Up or any other similar Bubble element, which will collect Data from the DataBase.

Apple sends different emails to one user, but the ID remains the same. So, you can apply a rule or do a search through the database, and if the user’s ID is already in your database, propose to use his original account.

Hope it will help you further.
Best regards.

[vinodbhadala]

Hi @Ecaterina,

I am using this plugin and successfully able to sign up users with Apple seamlessly. Thanks for this plugin and nice documentation. However, I am getting the issue that this does not keep users signed in when they come back to the app. I have correctly marked stay signed in as yes in workflows, however, it still does not seem to work. Can you please suggest how to get going over this issue?

[Ecaterina]

Hello, @vinodbhadala
Thanks for reaching out.

This behavior is related to the Bubble platforms functionality itself It is related to the temporary password, which is used for signing in with the Apple account.
However, please find 2 possible ways of fixing it (we have tested and they are workable):

1. You should use not the temporary password, but a real value, which will be saved in the DataBase:
   
   
   
   
   

Do not forget to apply the changes in the Backend Workflows too:

2. Usually, the user is signed in to the Bubble application for 24h. But in case you are willing to extend this option, you need to Log In your users after they will be signed in:
   
   
   
   
   

Please try these settings and let me know if they work now
Best regards,

[vinodbhadala]

Hi @Ecaterina ,

Thanks for sharing this with me. I have made changes as suggested, however, it still does not seem to be working. Can you please suggest to me or help me to understand it?