#kelvin_error
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1374950049305329664
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- kelvin_docs, 1 day ago, 11 messages
Hi @distant steppe can you share with us the full build error message?
Task :stripe_stripe-react-native:compileDebugKotlin FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
485 actionable tasks: 61 executed, 424 up-to-date
Looks like the warnings are coming from com/swmansion/rnscreens packag
For example
w: file:///Users/kelvin/Documents/pelago/pelago-traveller-mobile/node_modules/react-native-screens/android/src/paper/java/com/swmansion/rnscreens/FabricEnabledViewGroup.kt:9:48 'FabricViewStateManager' is deprecated. Deprecated in Java
Do they have a newer version of the library?
Is com.swmansion.rnscreens coming from a 3rd party libary that your project uses?
Looks like it's from https://github.com/software-mansion/react-native-screens
found it
is there anyway i can check which minimum version of react-native-screens need to be upgrade to satisfy requirement?
I believe this is a question to the developer of react-native-screens
thank Jack, will try to figure this thing out, appreciate
btw, not sure if this is a correct thread, when i'm using EmbeddedElement in iOS, if the amount <50 $ (SGD), it only show me GrabPay payment methods, is this a configure for my company account? how can i also show full payment methods as config in dashboard?
Sure we can continue the discussion here. Can you share with me the PaymentIntent ID?
technically i use the code example given here : https://docs.stripe.com/payments/mobile/accept-payment-embedded and no id passing to it yet
import React, { useState, useCallback, useEffect } from 'react';
import {
useEmbeddedPaymentElement,
IntentConfiguration,
EmbeddedPaymentElementConfiguration,
PaymentMethod,
IntentCreationCallbackParams,
} from '@stripe/stripe-react-native';
function MyCheckoutComponent() {
const [intentConfig, setIntentConfig] = useState<IntentConfiguration | null>(null);
const [elementConfig, setElementConfig] = useState<EmbeddedPaymentElementConfiguration | null>(null);
const initialize = useCallback(() => {
const newIntentConfig: IntentConfiguration = {
mode: {
amount: 100,
currencyCode: 'SGD',
},
paymentMethodTypes: [],
// Change paymentMethodTypes to customize the payment methods you want to accept
confirmHandler: async (
paymentMethod: PaymentMethod.Result,
shouldSavePaymentMethod: boolean,
callback: (params: IntentCreationCallbackParams) => void
) => {
// ...explained later
},
};
const newElementConfig: EmbeddedPaymentElementConfiguration = {
merchantDisplayName: 'Your Business Name',
returnURL: 'your-app://stripe-redirect',
};
setIntentConfig(newIntentConfig);
setElementConfig(newElementConfig);
}, []);
const {
embeddedPaymentElementView,
paymentOption,
confirm,
update,
clearPaymentOption,
loadingError,
} = useEmbeddedPaymentElement(
intentConfig!,
elementConfig!
);
useEffect(() => {
initialize();
}, [initialize]);
}
change amount < 50$ => only "GrabPay" shown, > 50$, all methods shown as expect
Ok, so you are using the deferred intent creation flow. Btw the amount that you specified is 100, which is only $1
Also you shouldn't set paymentMethodTypes if you want to use Dashboard settings to control the payment methods presented in PaymentSheet.
oh, might i ask why 100 is 1$ ?