#aleksandr_37787

1 messages ยท Page 1 of 1 (latest)

narrow garnetBOT
#

Hello! We'll be with you shortly. 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.

reef geyser
#

๐Ÿ‘‹ are you seeing this with your stripe app?

#

Ah yeah

#

hmm

#

I don't know tbh

#

let me ask a colleague

#

about this

rare hill
#

I see that c variable equals "sha256-" here:

waxen kiln
#

Hi there ๐Ÿ‘‹ I'm looking into this with my teammate. I searched our codebase and wasn't able to find the error message that you shared. Do you know if that is an error that is being surfaced by the code within your Stripe App?

rare hill
#

As I understand, the error message
Error parsing 'integrity' attribute ('sha256-'). The digest must be a valid, base64-encoded value. is generated by browser, because digest attr has invalid value.

#

This happens in place, where my application is inserted into document via script tag. Somehow digest attr is not valid. But after refresh I see that it exists in document with valid digest hash

waxen kiln
#

Hm, I'm really not sure about what could be going wrong here, or what needs to be done about it. I think this is going to need a closer look my by our teams that are more familiar with this side of Stripe Apps.

#

One quick question though, have you been seeing this behavior constantly, or was it working as you expected before but then changed? If the latter, do you have an estimate of when that change happened?

rare hill
#

It's difficult to say. Our app is not published publicly. It is under the development. We changed many things recently.
But thing that may be interesting to you is:

"post_install_action": {
    "type": "settings",
    "url": ""
  },

Now after application is installed, we redirect user to app settings page automatically to run after-installation actions.

#

After this redirect (post install action) appeared, I noticed this problem

waxen kiln
#

Hm, that is interesting. Out of curiosity, if you drop the url parameter there, since you're not redirecting to an external URL, does that help with the behavior at all?

Knowing this is specific to the redirect is helpful though, that helps narrow the scope of what we're looking at.

rare hill
#

it happens during app installation process. I don't control it. This code:

post_install_action": {
    "type": "settings",
    "url": ""
  },

is from stripe-app.json. Control is passed to our application just when settings page is open. But because of this error control can't be passed to the app. Only page refresh helps to mitigate this problem (after page refresh, app's code is run successfully)

waxen kiln
#

My understanding is you have control over that manifest file and can edit it as needed.

rare hill
#

oh, yes. wait a min

#

I've tried to change it with:

"post_install_action": {
    "type": "",
    "url": ""
  },

In this case after app installation I wasn't redirected to app settings page. I opened it manually and I saw the same error. And as before, after refresh, app was run.

waxen kiln
#

Can you try again, this time leaving "type": "settings" as you had it, and remove the url parameter completely instead. So it aligns with the sample shown here:
https://stripe.com/docs/stripe-apps/post-install-actions#link-to-settings

I'm not convinced this will fix the behavior you're seeing, and still think this will likely need a deeper investigation. However, I wanted to check as it's the only thing jumping out at me so far.

rare hill
#

url parameter is inserted automatically when I run "stripe apps upload"

waxen kiln
#

Ah, hm, well that shuts down that theory. Alright, I think it's time to get this into a support ticket so it can get to a team more familiar with this to take a closer look. Would you mind compiling the information you've gathered on how to reproduce this behavior into a ticket for us?
https://support.stripe.com/?contact=true