#cecilia_ios-appearance
1 messages · Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- cecilia-chen-_docs, 1 hour ago, 42 messages
- cecilia-chen-_error, 1 day ago, 21 messages
- cecilia-chen-_docs, 1 day ago, 55 messages
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1255645201989369917
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
is there way to remove the xmark button at the top left and the save address button at the bottom of the address element?
Hi 👋
If you embed the element directly then it will look weird, as you are seeing. No, there isn't a way for you to remove the X mark.
I can understand wanting to have a more integrated visual layout but there is a limited amount of visible space to work with and I suspect that is why we show implementing the address element as a full screen popover
ok, thanks! I will adapt the element like the documentation. I will keep the same visual
Okay cool! It looks like your integration is really coming along.
cecilia_ios-appearance
if I want to customize the appearance of the address component, should i change PaymentSheet.Appearance() using this doc? https://docs.stripe.com/elements/appearance-api?platform=ios
does address element sync with the paymentsheet? or i need to change the appearance of address element separately? is so, do you have the link for the doc?
where I can find all the possible font that stripe support?
oh, i think i can use custom font that i imported to the ios project
thanks, i think i got it
yes!
can someone help me with this? When I test it on real device, there are some white space on the top of the keyboard if the keyboard pops up, please see the attached screen recording.
I am using SwiftUI for this, so I wrapped the ViewController using UIViewControllerRepresentable, I'm not sure that is the reason caused the bug.
and then for my SwiftUI code:
strokedExtendedButton(label: isAddressSaved && addressDetails != nil ? "Edit service location" : "Add service location") { showAddressView.toggle() } .sheet(isPresented: $showAddressView) { AddressViewControllerWrapper(addressDetails: $addressDetails, isAddressSaved: $isAddressSaved) }
Uhm I haven’t seen it. In which secs of the video?
Oh I think this could be it https://github.com/stripe/stripe-ios/issues/2803
Can you try the suggestions of disabling SwiftUI's keyboard avoidance for UIViewControllerRepresentable here?
ok, let me read through this link
yeah it worked, and I found that I need to attatch .ignoresSafeArea(.keyboard) directly to the AddressViewControllerWrapper like this, otherwise, it won't work
strokedExtendedButton(label: isAddressSaved && addressDetails != nil ? "Edit service location" : "Add service location") { showAddressView.toggle() } .sheet(isPresented: $showAddressView) { AddressViewControllerWrapper(addressDetails: $addressDetails, isAddressSaved: $isAddressSaved) .ignoresSafeArea(.keyboard) }
I tried put .ignoresSafeArea(.keyboard) at the top of the .sheet line, and also the bottom of the .sheet line, only when i put it directly to AddressViewControllerWrapper will work
thank you!
Np and glad to hear you are unblocked
Hi Orakaro, does Stripe address element support saving the address to the customer's account? so that i can retrieve the address for future use, and the user doesn't need to fill in the address again?