Connor Turland comments

Results 339 comments of


                                            Connor Turland

Addition of `authorizeSigningCredentials` breaks ability for sandboxed hApps to initialise dynamically

oh, I see. cool!

Addition of `authorizeSigningCredentials` breaks ability for sandboxed hApps to initialise dynamically

we will see. It's hard to visualize without trying it

Addition of `authorizeSigningCredentials` breaks ability for sandboxed hApps to initialise dynamically

I am just getting some exposure to `hc launch` working with Wesley on something around the We app. Will report back...

Addition of `authorizeSigningCredentials` breaks ability for sandboxed hApps to initialise dynamically

seems, still untested, to be very much what is needed. Leaving this open for now but thanks for all the support! We haven't tried it yet

Addition of `authorizeSigningCredentials` breaks ability for sandboxed hApps to initialise dynamically

I just want to note that the signing credentials are portable, so you could acquire them in one context, and then bring them over to another and make authorized calls

Addition of `authorizeSigningCredentials` breaks ability for sandboxed hApps to initialise dynamically

I was just thinking of #1, another UI context, such as in a browser of choice. It would actually be useful to be able to have a `hc sandbox` call...

windows 64 - hc test issues

so this is resolved for you @ddw360 ?

windows 64 - hc test issues

what is your OS, nodejs version, and version of this code that you're running?

windows 64 - hc test issues

Can you try clearing the `test/node_modules` folder out, and then running `npm install` inside `test` directory?

windows 64 - hc test issues

Then rerunning the command you were trying?