Thank you for confirming your goal - much appreciated.
Based on your description, the issue may be due to one of the following reasons:
The âApple ID sign-in on successâ event may not be correctly linked to the plugin element on the page. Please make sure youâre referencing the correct element and that itâs visible and loaded when the action is triggered.
Ensure the âSign In with Appleâ plugin element is present on the same page (not inside a reusable element thatâs hidden or delayed) and properly initialized.
Try enabling Bubbleâs debug_mode to see whether the authentication is completing and whether the event is being skipped due to a condition or timing issue.
If everything seems to be in place, feel free to share a short Loom video or screenshots of your current setup, especially the plugin element configuration and the workflow event setup.
This will help us reproduce the issue and guide you further.
Just checking in to see if you had a chance to review our previous message. If youâre still facing the issue, feel free to share a short Loom video or screenshots of your plugin setup and workflow - this would help us guide you further.
@ZeroqodeSupport Hello - the plugin stopped returning the first and last names on successful login, is there a way to fix this? You can see below that the email address is returning correctly but both the first and last names are blank -
Please note that the first and last name are only returned on the userâs very first sign-in. This is a behavior defined by Apple, not the plugin itself.
If a user signs in again after the initial login, Apple does not send the name data again â only the email (if still authorized). This is expected and has been previously addressed in similar cases.
Thanks for the quick response. Would you mind please verifying this on your end? That is, that both the first and last names are getting returned? We had a video meeting with Apple tech yesterday about a number of items including this one, and on his first sign-in into our app, the first name did but the last name did NOT return. He had never used the app before. Iâve replicated this error in my dev environment as well. This functionality used to work, but something changed recently, maybe on the last update? This was one of the reasons that Apple rejected my app from the App store, but I havenât even touched this piece in awhile.
Weâve just tested the plugin on our end, and everything appears to be working correctly â both the first and last names are being returned as expected. Just a quick reminder: the plugin is designed to return user data only once per user (on their first sign-in). This is consistent with the behavior defined by Apple Sign In protocols and hasnât changed in recent updates.
To help us investigate further, could you please provide a short video demonstrating the issue? It would be especially helpful if you could include:
The steps to reproduce the error.
The plugin settings/configuration in your app.
This will allow us to better understand the scenario and attempt to replicate the issue on our side.
To understand better your use case, would it be convenient to share the following information:
â
-Screenshots/Video of your plugin elementâs configuration.
-Workflows associated with the plugin.
-Any additional details you believe are important for us to replicate and understand your use case.
â
Looking forward to your reply.
â
Best Regards,
Zeroqode Support Team
And when you step through the process, you can see below that the error is thrown after the user logs into their Apple account butbefore the âSigninwithApple sign-on successâ gets called:
Great, thank you. Do you have an ETA on their response? Iâm waiting on this getting fixed before submitting to the App Store - itâs why they failed my app last time.
We are excited to share that we have effectively resolved the issue with the Sign-in with Apple action and have updated it to version 1.48.0(Fixed problem with Last Name).
Could you kindly update the plugin within your app to this latest version and confirm whether everything is now operating smoothly?
Feel free to explore the pluginâs functionality on our demo page.
Your patience and cooperation throughout this process have been greatly appreciated.
Great, thank you, I checked and itâs working now. I wish it had taken less than 9 days and 4 very detailed messages from me before sending to the to the dev team. Hopefully, if there is a next time, we can reduce those numbers. That said, Iâm very grateful itâs fixed, thanks.
Glad to be helpful. Please feel free to reach us again when you need some help or assistance. It will be a pleasure to cooperate.
By the way, if you like our plugin you can rate it by going to the Plugins tab in Bubble editor. Find the plugin by name and give it as many stars as it deserves. We would appreciate it a lot!
Additionally, if youâre open to sharing your complete experience with Zeroqode, please feel free to do so here: Review
Hi Zeroqode team, do you plan to support native mobile for sign in with apple plugin ? Currently the element does not show for native beta but in the marketplace, plugin is marked as native mobile compatible
Weâve already followed up with you via email with the full details regarding your request. Please check your inbox when you get a chance, and feel free to reply there if you have any further questions.
Info from Zeroqode: âA mobile-ready version isnât planned just yet, but weâre actively working on expanding our support for native plugins as Bubble Native continues to evolve in its beta phase.â
Youâre absolutely right â our development team is currently working on making the Sign in with Apple plugin available for Bubble Mobile. That said, there are still a few limitations within the Bubble mobile environment that weâre working through. Development is in progress, and weâll be sure to notify you as soon as itâs ready.
Your email is already on the list to be informed once the plugin goes live.
