I am getting this error, while building my Angular app for SSR, and this line is from chatbot component inside interactions module, which I am not even using
var workerUrl = URL.createObjectURL(blob);
TypeError: Cannot read property 'createObjectURL' of undefined
Is there anyway to get rid of it?
Hello!! im newby here, i need some info for how i can paginate, count, and get first elements with offset from graphql api. Seems different as the usual grapql sintax....
Serverlessframework, which is working well, but again it just might be nice to have a single project where all of these pieces are managed.
Does anybody know if it's common / acceptable to build other cloud formation resource configurations into Amplify projects manually?
@kevin-mitchell it's entirely common and acceptable to put other non-Amplify AWS Resources in your stack. That's what the
amplify/backend/api/<api_name>/stacks/CustomResources.json file is for! You can put anything in there - including nested stacks which are stored somewhere else.
transcription: Transcription! @connection(name: "TranscriptionRegions")however providing any kind of value for this throws an error as well, saying it's not expecting the input.
expectedVersionin the schema for the
DeleteRegionInput, updating to the latest version
4.4.0(and regenerating the code) has solved the issue.
OK, here is one (btw, thank you @rrrix_gitlab for the response, sorry I'm just seeing it now!):
I have an
aws-exports.js that I believe is auto generated by the Amplify CLI. Inside of there, in the
oauth settings there is
"redirectSignIn": "http://localhost:3000/", "redirectSignOut": "http://localhost:3000/", "responseType": "code"
this is great for local development, but when I
amplify publish or want to push something to S3 for hosting / testing on my phone for example (or whatever), those values are pushed as well. I'm guessing this is because there is a deployment process that I should be following that would magically handle this... but I'm not sure what that deployment process is. Any tips?
I believe the preview message went out alongside this: