I have a storage bucket in google cloud and the url for the image is something like this
https://storage.cloud.google.com/my-bucket-name/image-name.png
then I use this link inside an email tempalte like this:
<a
href="https://www.my-url.com"
target="_blank"
><img
src="https://storage.cloud.google.com/my-bucket-name/image-name.png"
width="171"
height="41"
alt="some text"
style="display: block; border: 0;"
/></a>
And I'm send my emails using mailjet api, but when I recibe the email on my gmail I get the following as a src
https://ci6.googleusercontent.com/proxy/l_BzLY1sw86Ny3rRX4-7HxNe_rnkhWBS66tHaw7vzKOYYDswmLnHIt-EnTcZ7meI3d3n_tpAf6pXlRXepwGTVJg0oQg5mUdRtlTr2XJuoqPzhjSZvzeJb2z8Ldelk8fGpz4=s0-d-e1-ft#https://storage.cloud.google.com/my-bucket-name/image-name.png
But no image, only the alt text, if I try with hotmail, I can see the image on the web, but If I use the iphone email app, I have the same problem with gmail no image, no matter if I'm checking a gmail or hotmail account, also the same problem happen inside the gmail app no image.
I was checking the bucket configuration, but I don't see any other permission in order to allow gmail to show my image.
any help would be appreciated
you should always use "storage.googleapis.com/[BUCKET_NAME]/[OBJECT_NAME]" for application use.
Related
I'm getting backend failure error in google smart home while accessing fulfillment URL provided in dialogflow webhook url
{
textPayload: "SYNC: Request ID 1570058940383905256 failed with code: BACKEND_FAILURE"
insertId: "1trptjqgc2uhm9d"
resource: {
type: "assistant_action"
labels: {
action_id: "SMART_HOME_SYNC"
project_id: "gnextsmarthome"
version_id: ""
}
}
Action console Account linking details:
Authorization URL: https://accounts.google.com/o/oauth2/auth
Token URL :https://oauth2.googleapis.com/token
through voice assistant able to access fulfillment url successfully,but failed to access through google home while linking app.
also prebuilt smart home action option not visible in Action menu
I referred to this example to build smart home app:
https://github.com/shivasiddharth/google-actions-smarthome
In that example,they had used fake access token and auth url.
In order to use google signin concept, I have added google account token url: https://accounts.google.com/o/oauth2/auth and then end up with error 'Google account error'.(fig 1)
enter image description here
and also account linking type option is missing.but in this case able to see smart home prebuilt action(fig 2)
enter image description here
But later i noticed account linking type option become visible after enabling with dialogflow api.then 'google account error' is gone.
enter image description here
in this case i have mentioned fulfillment url in dialogflow webhook address to trigger smart home backend server function.
enter image description here
enter image description here
enter image description here
You are trying to use an endpoint which can’t be used and hence you will have to use your own endpoints as also mentioned in the comments on this answer. You can try out the Connect smart home devices to the Google Assistant codelab to see if the error is due to a configuration, or the server you are running behind your endpoint.
If you are still running into issues when implementing your own fulfillment endpoint, you can take a look at your error logs to see what the detailed debug string comes out as. You can learn more from the Troubleshooting Guide.
We have a simple Word Document (Private (no anonymous access)) hosted in Microsoft Azure BlobStorage Private Container with SAS Token enabled and now when we are using React Native Webview the document is unable to display did anyone came across similar issue?
return (
<WebView
source={{ uri: 'http://docs.google.com/gview?embedded=true&url=https://xyzgazd.blob.core.windows.net/schedules/file-sample_100kB.doc?sv=2018-08-18&sr=b&sig=usjflasjkflajskflafkjamb0AZwnnLhwy3-07-02T12%3A49%3A59Z&sp=r'}}
style={{ marginTop: 20 }}
/>
)
Please URL-encode your SAS token (including ? in front) and you should be able to see the content. I just tried with a text file in my storage account and it worked when I URL-encoded the SAS token. Without that, I was also getting the same error as you're getting.
Update: The below is the code based on above explanation:
var url = "https://xyzgazd.blob.core.windows.net/schedules/file-sample_100kB.doc?sv=2018-08-18&sr=b&sig=usjflasjkflajskflafkjamb0AZwnnLhwy3-07-02T12%3A49%3A59Z&sp=r"
<WebView
source={{ uri: 'http://docs.google.com/gview?embedded=true&url=' + encodedURIComponent(url)}}
style={{ marginTop: 20 }}
/>
I am using custom SignUp/SignIn policies and custom UI.
I have been through the posts on stackoverflow for "Forgot Your Password" functionality, which says the calling application need to read the error code and redirect to PasswordReset Policy.
When I Inspected the html, I found a href for forgotpassword link which is pointing to my signUpSignIn Policy.
<div class="password-label">
<label for="password">Password</label>
<a id="forgotPassword" tabindex="2" href="/domain.onmicrosoft.com/B2C_1A_signup_signin/api/CombinedSigninAndSignup/forgotPassword?csrf_token=xxxxxx&StateProperties=xxx & p=B2C_1A_signup_signin">Forgot your password?</a>
</div>
Is there any way that I can call the PasswordReset policy from the href directly, instead of catching the error code, as I am using custom policies.
Thanks,
You can send the user directly to the password reset policy from your application.
You can't send the user directly from a Sign-In/Sing-Up policy to the Password Reset Policy as described here.
UserVoice: Go Direct to Password Reset from Sign-In/Sign-Up
I have a custom button in Salesforce that has the javascript code to generate the docusign parameter with template id and recipient list CRL. And using demo docusign account for testing purpose. Here, am using docusign Salesforce Connect and not API.
Eventhough my email address is correct, when I click on the docusign custom button, I am getting an error message as follows,
Error: Incorrect email address format. Verify the email address or
contact your administrator for the correct format
But the docusign param generated values are correct for the email address,
https://dsfs.cs62.visual.force.com/apex/DocuSign_CreateEnvelope?
CES=Medical+Release+Form.pdf&
RES=0%2C0%2C0%2C0%2C0%2C0&
DST=E1377257-80EB-4F3D-A046-A1D033CBD4F5&
DSEID=0&
LA=0&
SourceID=5005C000000UNG1&
CEM=Please+sign+the+forms+given&
OCO=Send&
CRL=Email~+kamatchidevi%40mstsolutions.com%3BLastName~+test+doc+%3BRole~Signer1
Thanks & Regards,
Kamatchi Devi
The + signs are causing the issue here, there is also no need to encode it yourself as it's done by the manage package into the URL. However, if you are going to URL encode I would recommend doing the entire string, like so
CRL = encodeURIComponent('Email~kamatchidevi#mstsolutions.com;LastName~test doc;Role~Signer1')
I am trying to run this official GCM Notifications sample. This comes with no instructions so trying to figure out on my own.
Here is what I did:
Registered an app on Google Dev Console, enabled APIs for Google+ API, Google Cloud Messaging for Android and Google Cloud Messaging for Chrome
I downloaded the repo and removed 'Key' field from the manifest.json
I uploaded it under my chrome app developers account
I installed this app. And opened the extension location and copied key field from manifest.json
Opened the Chrome app. Used the project id of app I registered on dev console as Sender ID. After pressing Register it said: 'Registration succeeded. Run the following command to send a message.'
Now it has three fields App Key, Message Key and Message Value. So in App key I entered key which I got from manifest.json and in both fields of Message Key and Message Value I entered Test and Hello world respectively.
It gave me a command like:
curl -H "Content-Type:application/x-www-form-urlencoded;charset=UTF-8" -H "Authorization: key=Mg...AB" -d "registration_id=AP...tQ" -d data.test=hello https://android.googleapis.com/gcm/send
When I run this from my local machine, I am getting following error:
<HTML>
<HEAD>
<TITLE>Unauthorized</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Unauthorized</H1>
<H2>Error 401</H2>
</BODY>
</HTML>
The "Authorization: key" is not the key in the manifest.json file. It is the API key, which you get from the Developers Console. (Leave a comment if you can't find the API key, and I'll provide more detailed instructions.)
As the API has evolved into what is now the GCM API, the terminology has changed, and its usage by Google is inconcistent.