the Issuer has not made this pass available to you ? about rest-samples HOT 11 CLOSED

hi @ncalteen all good now , you 're the issuer account was not properly setup, but once google approved the account all went fine

from rest-samples.

https://pay.google.com/gp/v/save/eyJhbGciOiJSUzI1NiJ9.eyJpc3MiOiJ0bi1hYmMtdGVzdEB2aWJyYW50LXJldGluYS0yODAzMTQuaWFtLmdzZXJ2aWNlYWNjb3VudC5jb20iLCJhdWQiOiJnb29nbGUiLCJ0eXAiOiJzYXZldG93YWxsZXQiLCJpYXQiOjE2NjE1MzY5MTMsInBheWxvYWQiOnsiZ2VuZXJpY09iamVjdHMiOlt7ImlkIjoiMzM4ODAwMDAwMDAyMjEyODY0OC5QRVJTRVItTUFDLTIxMDAwMjAifV19LCJvcmlnaW5zIjpbXX0.nrtVK_cjRNXSs4bckw1U1b8A1YtccxTV5oF25fop-YnJBMItWxUSy5mW1hKX6ywyJvl3BT9UV7GiIa16LcLDQWfPc6UlxCHBzNe4WR_uNpofqLD0Z71vv3-nrDMc1WOAMZFAhqWAzvCu-i_HI_wVHIQ41dANnsIZ1Oqz5lYLq4lhxhCpfnyDlrh7ZDTTpKx2zsiiKdA7J2Ixhm6bZ9qxAP-TyOvAIMBYaW_Jv8O0WAJdrX9DKh53gonEWXo-GQUZmWl3gVJk8zqLnJdpyZH7uEnSUq0mG1cVAj0HyyAxdDaEuZrgnL414e04hCqXcHAuByRpFLUS5-eCAkzysbEqkA

from rest-samples.

Hello,

Apologies for the delay getting back to you on this. My initial thought was that the issue could be related to invalid time intervals for the pass object. In testing, however, I was unable to reproduce the issue.

Would you be able to provide the pass object definition (removing any sensitive data)?

from rest-samples.

Hello again,

After doing some further research, this may be your issuer account being in developer mode. The best course of action would be to contact Google Wallet support to assist.

from rest-samples.

can this repo be used with a google temporary issuer account? I'm getting this same error

from rest-samples.

I'll reopen this issue and test it out. I'll send another response soon!

from rest-samples.

I did some testing and came to the following results:

If I create a temporary issuer account using my regular email, I get a "something went wrong" error when using the JWT creation methods in this repository (testing with the Python create_jwt_save_url method). This is because the JWT is signed by the service account key used in the auth method, which does not have permissions to the temporary issuer account.

However, if I create the temporary issuer account using my service account email, I get the same error as you. This is because the temporary issuer accounts are in developer mode (the same issue you faced originally). They are intentionally set up this way, so only email addresses that have permissions to the issuer account are able to save the passes.

One solution that could work in your case would be to create another issuer account that is a "child" of your main issuer account. This way you do not need to populate your main issuer account with test passes. When you create a new issuer account using one that is already approved, it will also be approved automatically. The steps below outline how to do this:

1. Using your service account credentials and your existing issuer account, call create_issuer_account to create a new issuer account. Make sure to give it a name and email that identify it as used for testing.

   new_issuer_id = demo.create_issuer_account(issuer_name="MyCompany - TEST",
                                              issuer_email="[email protected]")

2. Next, update the permissions of the issuer account to include any email addresses that need access to create/edit passes.

   demo.update_issuer_account_permissions(issuer_id=new_issuer_id,
                                          permissions:[
                                              {
                                                  "emailAddress": "[email protected]",
                                                  "role": "OWNER"
                                              }, # repeat for each email/role
                                          ])

After that, you should be able to use this issuer ID for testing purposes.

Please let me know if this helps, and if you have any other questions!

from rest-samples.

Thanks for taking the time to respond.
I tried your suggestion, and the call to create_issuer_account yields the following error:

{ "error": { "code": 403, "message": "Service account or user must already be shared with a non suspended issuer.", "errors": [ { "message": "Service account or user must already be shared with a non suspended issuer.", "domain": "walletobjects", "reason": "permissionDenied" } ] } }

I get this error for all values of issuer_email, I tried my google account email, the service account which the temporary issuer account is linked to, and creating a second service account in google cloud console and giving it owner status. Even with a string which is not a valid email, the error is the same.

from rest-samples.

How long ago did you create the temporary issuer account? They are only valid for 7 days.

Also, the create_issuer_account call must be made with a service account associated with a non-temporary issuer account (one you created in the Google Pay and Wallet Console).

from rest-samples.

sorry about the delay responding, I'm reasonably sure the issuer account wasn't expired at the time (but I might've been wrong), but it would definitely be by now. If create_issuer_account must be called using a non temporary account, how could this be used to create an issuer account that wasn't in developer mode?

from rest-samples.

Hello,

If the calling issuer account is in developer mode, then any accounts it creates will also be in developer mode. In order to create production issuer accounts, you would first need a production account. To get the first one, you would need to reach out to Google Support. If you go into the Google Pay & Wallet Console, the Contact support option should get you in contact with someone who can help you with getting the main account approved.

I hope this helps!

from rest-samples.