I am using expo to work on my app and wanted to send a link to a friend to test it out. When I click on "send link with email..." I get an error message:
oops, sending link to 'friendsemail#gmail.com' failed."
I haven't published the app to expo, so I was curious if I need to do this before I am able to send the link. Is this a bug or am I missing a step before I can share the expo link?
I have tried to restart the metro bundler, restart the terminal, but neither are working. I am about to join the expo slack group but wanted to see if this was an issue others have ran into and have a quick solve for.
thanks!
Have you signed into Expo on your development machine? You can do this by pressing 's' key. After signing in, try sending the mail, it should work.
See the image below:
You need to sign in with your expo account. Press 's' key in terminal, you will get option of sign in . After successful signing in try again sending mail, it should work.
Related
After sending a new build to the app store, the push notifications for my app are no longer working. During the build, expo made a new APNS certificate, and now when I try to push a notification to users, I get the following error message.
"'{"errorMessage":"Invalid
Credentials","channelType":"APNS","pushProviderStatusCode":"403","pushProviderError":"InvalidProviderToken","pushProviderResponse":"{\"reason\":\"InvalidProviderToken\"}"}'"
I get the same error message when attempting to send myself a notification through the AWS Console. I tried to update my push notification credentials on expo, but get a similar error:
? Path to P8 file: /Users/REDACTED/Downloads/AuthKey_D3QREDACTED-1.p8
? Key ID: REDACTED ? Apple Team ID: REDACTED Unable to validate Push
Keys due to insufficient Apple Credentials
I tried following every thread I could find online about the error and verified that I had the right Team ID and Key ID, but it still does not work.
Happy to provide more info if needed, and thank you for your help
I just had to regenerate a new .p8 file and upload it to AWS pinpoint
I had this issue recently, and no matter how many times I tired to "Edit" the APNs configuration it would not work. Eventually I just removed APNs setting from PinPoint, saved it, and then set it up again fresh.
Now it works.
I'm trying to use bigrquery from an interactive R session for the first time. I've installed the R bigrquery package and successfully established a connection. I've authenticated following a redirect from the interactive RStudio session to the web browser for login, so oauth seems to be working correctly. However, when I try to run a query, such as DBI::dbReadTable(con, "A549_raw_merged_TADs")[1:6, ], I get the error Error: The project variant-annotation has not enabled BigQuery. [invalid].
I am sure I need to enable something else in the project on the Google side, but I'm not sure what I need to enable, or how to do that from the web console interface.
Is this documented anywhere, or can anyone here give me instructions?
Note: I have confirmed that the BigQuery API has Activation status of Enabled via the console at https://console.cloud.google.com/apis/api/bigquery-json.googleapis.com/overview, so although my question is the same as Error processing job: Project has not enabled BigQuery, the issue appears to be different.
Additional information: when I check the BigQuery API status via the console link above, there's a notification that "To use this API, you may need credentials. Click 'Create credentials' to get started."
So it may be that my assumption that oauth seems to be working is not correct.
You can enable the BigQuery API with this command gcloud services enable bigquery.googleapis.com, but, since you mention it is already enabled, you may be pointing to a different project.
Feel free to ping me on a new thread if you require assistance on the new issue.
I am unable to sign out from Cognito after connecting with AES Amplify via withAuthenticator.
The first time the app shows up, it presents the login screen. After logging in it works normally. Then if I call:
Auth.signOut()
It gives the error:
null is not an object (evaluating 'this.credentials.clearCachedId')
and stays logged in. Same with the Greetings sign out buttom from Amplify. I just can't sign out. It seems to happen when using tab navigators.
Any ideas? Thanks in advance.
Hey I think this have been solved in the latest version. Could you update the library and try again?
I've gotten WSO2 working on the server. I can login through the management console and EMM, publisher, and store are all working. I can create a new user through the EMM dashboard, and the email is sent correctly. So everything is fine while using the website.
I'm using the sample APK that comes with WSO2 to do some development, but every time I try to register the app pops up "Authentication Failed - Cannot proceed the authentication. Please contact an administrator." And there is no output in the console when this happens.
If I put in the incorrect credentials I get a separate error, "Authentication Failed - Incorrect login information. Please try again." So I know my credentials are correct.
What does this mean? Is there another place to find more detailed logs?
Have you tried debugging the Android-agent ? If so you might be able to provide more information regarding this issue by looking at agent debug logs.
BTW did you tried enrolling as the admin user?
I have WSO2 EMM version 1.1.0 set up. I have the certs all working and everything is playing nicely. I compiled the IOS client and have it installed on my phone via OTA. I am in the process of registering my device. I have a user setup and I have the proper password. I can successfully login from the registration page on my phone and I get the profile downloaded and it has the green "Verified" message on the profile. The problem occurs when I press the install button on the profile. I get a activity spinner at the top of the screen and it says "Installing Profile". It spins for about 30-60 seconds and then I get a message stating "Profile Installation Failed. The request timed out". Any ideas on what would be causing this?
Thanks
Go to {emm_home}/repository/conf/emm-config.xml and chehck whether the following entries are properly pointed to your server.
<iOSEnrollURL>https://10.10.10.174:9443/emm/scep</iOSEnrollURL>
<iOSProfileURL>https://10.10.10.174:9443/emm/profile</iOSProfileURL>
<iOSCheckinURL>https://10.10.10.174:9443/emm/checkin</iOSCheckinURL>
<iOSServerURL>https://10.10.10.174:9443/emm/server</iOSServerURL>
<!-- post url for device tokens -->
<TokenURL>http://10.10.10.174:9763/emm/api/devices/iostokenregister</TokenURL>