stripe-java | Java library for the Stripe API | Ecommerce library

This sample includes both example Android client and a Java server implementations. You should be able to clone the repository and follow the appropriate READMEs to run those examples and see how this works. Follow along with the guide and if you have more specific questions please raise those.

You will need to be able to install and build android & java to run this, of course.

stripe-java is pinned to a specific API version. When you upgrade to a new major version in the library it usually contains breaking changes and/or an upgrade to the most recent API version. This is what happened in 20.0.0 as documented here where the library was pinned to 2020-08-27.

That new API version has a lot of changes including some cleanup on the Customer resource. Stripe stopped returning sub-lists by default: subscription, tax_ids and sources are not returned unless you explicitly expand those sub-lists directly. This allows the API to be faster in most cases and to selectively select the sub-lists you need in specific parts of your code.

In Java, this means that you need to expand the sources collection if you want to be able to create/attach a new card. This is also documented in the API reference here and the code looks like this:

This : stripeCustomer.getSources() will be null in v20.0.0 and above of the library because it pins to API version 2020-08-27 where customer.sources was removed by default. [0] [1]

The sources property on Customers is no longer included by default. You can expand the list but for performance reasons we recommended against doing so unless needed.

You would need to explicitly expand [2] "sources" when retrieving the Customer in order to populate customer.getSources()

1. Please check the connectivity between the node in which application is deployed and the instance in which DB is there.
2. Have you provided enough permissions for both nodes for communications ?.
3. Do ping from application machine to db machine.
4. Install mysql client in application machine and try to connect to the db.
5. Is the database available in that database server ?

Check that those properties are actually defined in application.properties. There is also an application-aws.properties file, if the properties are only in that file then you will need to tell Spring Boot to enable the aws profile with SPRING_PROFILES_ACTIVE=aws, or add the aws properties with empty values in application.properties.

If no Spring Boot profile is activated, it will only use the properties defined in application.properties.

If you enable the aws profile, it will use use properties from application.properties as defaults, and then any matching properties defined in application-aws.properties will override those from application.properties if defined.

If what you are trying to do it only use those AWS properties when deployed to AWS, then you might need to make a Configuration object that holds those properties in it(which is a better practice than including properties with @Value in code), and make the AmazonS3 bean creation conditional on those properties being set.

Given that your project structure is a standard Maven structure, convention over configuration should apply and there should be no need to try and explicitly include application.properties with additional class path configuration. I.e everything under /src/main/resources should be available on the class path and to the application at runtime.

It was my bad. After I moved the code from test to integration folder, some resources inside (those which are responsible for initializing the classes) were pointing to the old directory test, not integration. The Gradle build file is correct.

So, turns out this issue was due to mismatch between play services/support library versions my app was depending on directly and transitive dependences from FirebaseUI - https://github.com/firebase/FirebaseUI-Android#upgrading-dependencies

First make sure it works when running sbt it:test or if you use sub-modules sbt module/it:test

If it doesn't sbt has this great resource: https://www.scala-sbt.org/1.x/docs/Testing.html#Integration+Tests

As a template for a working setup, a build.sbt:

As per the error. You need to

Configuration on demand is not supported by the current version of the Android Gradle plugin since you are using Gradle version 4.6 or above. Suggestion: disable configuration on demand by setting org.gradle.configureondemand=false in your gradle.properties file or use a Gradle version less than 4.6.

so do