The bounty expires in 2 days. Answers to this question are eligible for a +50 reputation bounty.
Jimmie Johansson wants to draw more attention to this question.
I have run through AWS Amplify's full-stack application tutorials multiple times to create a react native app, every time with the same result. The UI components created in AWS Amplify Studio are not being synced to my local codebase on pull.
The steps I followed on my most recent attempt:
Create Amplify app via AWS Amplify console
Configure UI Components/sync with Figma
Using the "Local Setup Instructions" link at the top right of Amplify studio, performed an amplify pull
The amplify pull always succeeds but never pulls UI components. If I set up a backend data or auth, I will see those synced properly, but I never see this (screenshot from a youtube vid):
And no ui-components folder is created in my source code. I'm at a loss, I've watched videos and followed tutorials from different people and nothing seems to work. The results are always the same and the rest of the functionality works as expected (graphql schema, auth, etc).
I found this question, which is similar, but outdated as from what I can tell Amplify should now support react native.
Related
I have a small personal-use only app that logs into a [throw away] gmail account to pull out an auth-token so it can then run a scheduled job (turning on/off my home cameras). Its dead simple and works, except that the app is in GCP TEST mode and it looks like the gmail auth expires in 7 days.
I highly doubt based on the below requirements that I can promote the app, and I dont want to publish it regardless. I tried GCP Support and wound up here. Im sure Im not the only person that has dealt with the 7 day expiration on a personal project. Any ideas?
If you check the documentation for oauth2#expiration
A Google Cloud Platform project with an OAuth consent screen configured for an external user type and a publishing status of "Testing" is issued a refresh token expiring in 7 days.
The key hear is setting your project into production.
What you are showing in that image are requirements for application verification. You shouldn't have to go though verification for a single user app.
Try just setting it to prodcution and then wait a week and see if it still expires. It shouldn't
I highly doubt based on the below requirements
Unfortunately with the new security restrictions. I wouldn't doubt anything these days. They keep changing the rules.
I have just started using Amplify to build my web app, and set Web Preview by connecting with Github (followed here).
Even though Amplify App is integrated into my Github organization/repository, Web Preview does not get triggered and no pull requests are shown.
Could you tell me what causes this and how to solve the problem?
(e.g., Need to use Github Team/Enterprise plan?)
I built a flutter web application and have previously whole backend setup on AWS. So I want to use my existing userpools from cognito in my app. But just got know that AWS amplify for flutter in only supported in android and ios,not for web. Can you suggest me any solution for this?
Try using this package: https://pub.dev/packages/amazon_cognito_identity_dart_2
I've been using it for a while, and it works fine on Android and Web; I think I even got it working on iOS.
What Amplify team did with official Flutter package was use a wrapper around existing Android and iOS implementation (by using platform channel). I guess this is a reason it will take them a while to sort out web.
The above package is based on amplify-js, and re-written in dart, so it will compile on any platform.
In my project workspace I created two separate projects: one with amplify to create back-end objects, and one flutter project. So, like in your case, my flutter project connects to an existing AWS backed.
Stack: Expo React Native, expo-branch
I am searching for a way to track Facebook Campaign Ad Installs with Expo in the managed workflow. I have integrated expo-branch (link below) and set up the integration between Facebook Ad Manager and Branch. As it stands, Branch is not getting the IDFA, which I suspect is the reason I am getting no analytics on Facebook through any ad campaigns. It looks like Expo has restricted access to the IDFA and I'm wondering if anybody has found a viable workaround (without detaching from Expo).
References:
https://docs.expo.io/versions/latest/sdk/branch/
https://forums.expo.io/t/latest-expo-branch-excluding-the-idfa-code/44357
A Branchster here:
For SAN(self attributing networks) like Google and Facebook, it is necessary that the Branch SDK correctly captures the device identifiers for the SAN integration to work and you be able to see attributed Installs and downstream events. Since there is not much support for Expo in the managed workflow, we would suggest using Bare workflow. Alternatively, you can reference our complete SDK support here.
I am trying to setup Cloud Datastore, in GCP. Upon selecting "Cloud Datastore", in console, I see the "Choose where to store your data" page, with this error:
"Unable to retrieve database locations
There was a problem retrieving the available storage locations for your data. Retry or return later to finish getting set up."
Has anybody encountered this?
I have encountered same and resolved as below. (Iam using free tier)
When you select a location in either product (Cloud Datastore or App Engine), you set the location for your entire Google Cloud Platform project. I choose location to set from App Engine.
From Home (on left side) --> App Engine --> Select a language (I have selected "python"). --> It prompts for location (I have selected "us-central") --> (press) Next
Thats it come out of the tutorial. Next time I selected Datastore, it worked fine.
Hope this helps (screens below)
SCREEN1
SCREEN2
SCREEN3
SCREEN4
I've encountered the exact same error. Some of the Google Cloud management tools are a bit buggy, gcloud included, they need more TLC and more users to report bugs to Google. The best way around the bugs is to either use the Firebase Console or the App Engine console. Either one of these two appear to be required to provide the missing management glue between the various Cloud products Google has. The Firebase console IMHO is superior to the app engine console, and that's what I would recommend using. You can create the DB from the Firebase console. it will also add Firebase to your project, giving you access to the Firebase CLI, which works very well and doesn't have all the bugs that gcloud CLI has.
Go to https://console.firebase.google.com/u/0/ to open the firebase console
Click on +Add Project and select the project you created using the Google Cloud Console.
This will prompt you to accept addind Firebase for this project. Click accept, it will enable access to the project via the Firebase emulator and firebase CLI, you definitely want this.
Under Develop in the left hand menu, select Database, from there you will be able to add the version you want. Keep in mind only the old firestore has an SLA, but the new native Cloud Datastore is better, it has the pub/sub on events on read/writes.
I use Firebase to manage microservices that are only accessible via special routing from other backends and don't use any Firebase client code, it's just so much easier to manage the functions and run them locally with the firebase emulator before deploying using the Firebase CLI. I've not had the same luck with gcloud or using the Google cloud console as opposed to the Firebase console. On the other hand, Firebase CLI, the emulator and the Firebase console are fantastic, pretty seamless experience. It's been a joy using them. I wish I could say the same about the Cloud console, I go in there only when truly necessary.