App crash when using apple pay
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 30/100
- Type d'issue
- Bug
- Clarté
- À clarifier
- Activité
- À l'abandon
- Stack technique
- ios, typescript
Piste de recherche
Start with the Apple Pay authorization handler at node_modules/@nativescript/apple-pay/payment-authorization-view-controller-delegate.ios.js:43 and trace the request and paymentData shown in the issue. Reproduce the crash using the provided onApplePayTap flow, then verify that authorization no longer terminates the application and the payment sheet completes normally.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Error:
***** Fatal JavaScript exception - application has been terminated. *****
NativeScript encountered a fatal error: Uncaught Error: The data couldn’t be read because it isn’t in the correct format.
at
PKPaymentAuthorizationViewControllerDelegateImpl.paymentAuthorizationViewControllerDidAuthorizePaymentHandler(file: src/webpack:/vois-mgov/node_modules/@nativescript/apple-pay/payment-authorization-view-controller-delegate.ios.js:43:0)
(CoreFoundation) *** Terminating app due to uncaught exception 'NativeScript encountered a fatal error: Uncaught Error: The data couldn’t be read because it isn’t in the correct format.
at
PKPaymentAuthorizationViewControllerDelegateImpl.paymentAuthorizationViewControllerDidAuthorizePaymentHandler(file: src/webpack:/vois-mgov/node_modules/@nativescript/apple-pay/payment-authorization-view-controller-delegate.ios.js:43:0)
', reason: '(null)'
*** First throw call stack:
(
0 CoreFoundation 0x00007fff20406d44 __exceptionPreprocess + 242
1 libobjc.A.dylib 0x00007fff201a4a65 objc_exception_throw + 48
2 NativeScript 0x000000010610de7e __copy_helper_block_e8_32o + 0
3 libdispatch.dylib 0x00007fff201148e4 _dispatch_call_block_and_release + 12
4 libdispatch.dylib 0x00007fff20115b25 _dispatch_client_callout + 8
5 libdispatch.dylib 0x00007fff20123043 _dispatch_main_queue_drain + 1050
6 libdispatch.dylib 0x00007fff20122c1b _dispatch_main_queue_callback_4
code:
const MERCHANTID = '388333172821828292929';
const SomeIdentifierFromPaymentProvider = '89290109290129912088';
export const onApplePayTap = async (args?: any) => {
//try {
// just ensuring this runs only on iOS
if (isIOS) {
const applePayBtn = args.object as ApplePayBtn
// setup the event listeners for the delegate for apple pay for our button
applePayBtn.once(ApplePayEvents.DidAuthorizePaymentHandler, async (args: any) => {
console.log('in authorize handler')
console.log(ApplePayEvents.DidAuthorizePaymentHandler)
// this is where you do backend processing with your payment provider (Stripe, PayPal, etc.)
// this payload is just a sample, your payload to a provider will likely be different
// you can see here how to access the encrypted values from Apple Pay inside the `args.data.paymentData`
const payloadToBackend = {
transaction_type: 'purchase',
merchant_ref: args.data.paymentData.header.transactionId,
method: '3DS',
'3DS': {
merchantIdentifier: SomeIdentifierFromPaymentProvider,
data: args.data.paymentData.data,
signature: args.data.paymentData.signature,
version: args.data.paymentData.version,
header: args.data.paymentData.header
}
}
const result = true //await this.someHttpMethodToYourProviderBackend(payloadToBackend)
if (result) {
// need this to call when the payment is successful to close the payment sheet correctly on iOS
args.completion(ApplePayTransactionStatus.Success)
// now you can follow through with your user flow since the transaction has been successful with your provider
} else {
// payment failed on the backend, so show the FAILURE to close the Apple Pay sheet
args.completion(ApplePayTransactionStatus.Failure)
}
})
// these are the items your customer is paying for
const paymentItems = ([
{
amount: 20.5,
label: 'Balance',
type: ApplePayPaymentItemType.Final
}
] as unknown) as ApplePayItems[]
const request = {
paymentItems,
merchantId: MERCHANTID // the merchant ID for this app
merchantCapabilities: ApplePayMerchantCapability.ThreeDS,
countryCode: 'US',
currencyCode: 'USD',
shippingContactFields: [ApplePayContactFields.Name, ApplePayContactFields.PostalAddress],
billingContactFields: [ApplePayContactFields.Name, ApplePayContactFields.PostalAddress],
supportedNetworks: [
ApplePayNetworks.Amex,
ApplePayNetworks.Visa,
ApplePayNetworks.Discover,
ApplePayNetworks.MasterCard
]
} as ApplePayRequest
// `createPaymentRequest` will call into the Apple Pay SDK and present the user with the payment sheet for the configuration provided
await applePayBtn.createPaymentRequest(request).catch((err) => {
console.log('Apple Pay Error', err)
})
}
- Langage dominant
- TypeScript
- Étoiles
- 35
- Forks
- 13
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de NativeScript/payments
-
com.android.billingclient:billing@@8.0.0 - com.google.android.gms.internal.play_billing.zzbg.zzeOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 28/100
NativeScript/payments#45 ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
NativeScript/payments#43 · 2 réactions ·
-
[@nativescript/payments] Not possible to use both subscriptions and IAPs in the same projectOuverte
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
NativeScript/payments#39 ·
-
support Amazon Android appsOuverte
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
NativeScript/payments#36 · 2 commentaires ·
-
[Restore Orders] MistakeOuverte
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
NativeScript/payments#35 ·
Toutes les issues de NativeScript/payments
Issues similaires
-
test: claim-conflict drop leaves both facts active and is never re-proposed (untested review cell)Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
Les mainteneurs répondent en général sous 1 jour
-
[Feature]: Usage page should show API-equivalent cost and say when a connected plan shows info onlyOuverteenhancement from-x
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
nightly-labs/openbot#4867 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
egonSchiele/agency-lang#1377 ·
Les mainteneurs répondent en général sous 1 jour
-
normalizePath removes the Windows device namespace prefixPeut-être pris Une pull request liée à cette issue est ouverte ou déjà fusionnée. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
caprover/caprover-frontend#273 ·
Les mainteneurs répondent en général sous 1 jour