Hi - you can apply for App Builder trial at https://adobe.ly/appbuilder-trial. Once your IMS org is enabled for the trial program, you will be able to create new project with template "App Builder".

Endpoints for updating Runtime actions are:adobeioruntime.net *.adobeioruntime.net If you project has a UI, it will need to upload static files to our CDN. The upload URL can be dynamic based on the backend system so I can not confirm it. Currently it's uploaded to AWS S3.

@Saif - based on the previous conversation, it seemed that your connection is blocked by a firewall.Similar report at https://github.com/adobe/aio-cli/issues/222Did you have a chance to work with your IT department on how to overcome it?

@suryapramodhd73 - to make sure I understand the problem correctly, please confirm:the error you described in the original question only occurred in prod namespace, both when you used `stateLib.init()` and `stateLib.init({ ow: { namespace, auth } })`.there was no error in other namespaces, both when you used `stateLib.init()` and `stateLib.init({ ow: { namespace, auth } })`.

@SahithiMalyala - I got your requirement, but why isn't this solution working?In your App Builder project, there are different workspaces for prod, stage, dev, etc. Each comes with its own Runtime namespace.If you deploy your app to a namespace, let's say dev, libState.init (without any param) will automatically pick the dev namespace. And the libState data is specific to that dev namespace only.If you deploy to stage later, you will have fresh data of stage. And the same for prod.In summary, th...

@SahithiMalyala - could you try state init without custom ow auth. Simply this:let state = await libState.init();Why do you need to pass the custom Openwhisk namespace + auth?

As discussed in direct conversation: it's expected that the order of key-value pairs in a JSON object is not quaranteed. If the library consuming it requires a specific order in the (stringified) JSON object, you could manually construct a raw string with the desired order, taking values from the original request body.

@Naveen_Srinivas - regarding the different output order of JSON params, that's expected because it's a JSON object, not an array. So the order doesn't really matter here, because you get an item by `params['keyName'].For your second question, your action gets a request body in JSON, so it automatically parses it to a JSON object. The "__ow_body" param is only available and useful for non-JSON request body. See https://github.com/apache/openwhisk/blob/master/docs/webactions.md#http-context for mo...