wqpvery.blogg.se

Instead of returning false 10+ times, just return false at the end since the only case you'll return true is if the case is 0.Use ReceiptValidator\iTunes\ Validator as iTunesValidator

("Unknown error: status code = " + status) ** unknown error code (nevertheless a problem) */ (status + ": Production receipt sent to Sandbox environment") (status + ": Sandbox receipt sent to Production environment") (status + ": Receipt valid but sub expired") (status + ": Receipt server unavailable") (status + ": Shared secret does not match") (status + ": Receipt not authenticated") Is there a better way to do this? public class AppleReceiptValidator etc. Those booleans are used for settings such as whether to use the sandbox or not. Last, but not least, I'm using boxed Booleans in the constructor and isValid so those parameters can be null. OR Optional isValidReturnReponse(String receiptData, Boolean In this method, I'm considering return either an Optional or maybe an Either: Either isValidReturnReponse(String receiptData, Boolean Second, I'm considering adding a method to return both validate and return the entire response of the receipt validation. In the response (see the Parse the Reponse section), there are fields that might be of importance. Before my second question, for context, the receipt is sent to Apple's servers for validation.

First, should I change the statements to instead be logs (like slf4j)? Or omit them entirely? I'm considering seriously developing this as a library. In my implementation, one of the classes I want to improve is AppleReceiptValidator. I based it mostly on the gdx-pay-server library. I'm working on a solution for validating Apple receipts.