I'm working on a notification push server and want to push a live tile with an image URL (external server).
The problem is that I can't get it to show as BackgroundImage on the applicatoin tile. As far as I understand the documentation it should be possible as long as the URL is valid, not https, some size restrictions, etc.
I comply with all the restrictions given, but can't get my image from the external URL to show on the tile. Local files work though. I'm searching for hours. Can anybody tell me if it's possible or did some rules change since mango or something?
URL restrictions: http://msdn.microsoft.com/en-us/library/windows/apps/hh465403.aspx#urls
And of course; as soon as I submitted the ticket I found the 'ListOfAllowedDomains' that should be set to the channel.
Related
The FDL has been working fine in production for a few weeks and has suddenly started show this error in the browser as if it does not have a valid SSL certificate.
The FDL is generated via the API.
Is there a solution to remove this warning for my FDL?
I have raised a support request with GCP but have posted a question in here in case there is something I can do.
Turns out a received an email from Firebase about this 1 working day ago (before the weekend so I did not notice it).
I followed the instructions and several hours later it was working so I am assuming this was the issue.
Note it did not fix the issue immediately.
We’re writing to let you know that your Firebase Dynamic Links (FDL)
project(s) did not have configuration to prevent phishing, so we
generated Allowlist URLs that your Dynamic Links can redirect to.
Specifying a URL allowlist prevents third parties from using your API
key to create Dynamic Links that redirect from your FDL domain to
sites not on the allowlist.
What do I need to do? Review the generated URLs or to add additional
URLs:
Click 3 dot menu icon> Allowlist URL pattern from the Engage > Dynamic
Links page of the Firebase console for each project. Review the
auto-generated allowlist URLs to ensure they cover your intended link
destinations. [Optional] Specify up to ten regular expressions for
additional allowed URLs using RE2 syntax. See the images below for
clarity.
Only URLs that match one of your configured regular expressions can be
successfully used as a Dynamic Link's deep link or fallback link.
Your impacted project(s):
project1 project2
To learn more, see the Allow specific URL patterns documentation.
Feel free to reach out to our Firebase support team for more
assistance.
This issue I tried to reproduce:
I can able to reproduce if in My device setting time zone if I set date older then 1 month then this error will come.
I'm running a Telegram network where I post discounts from Amazon on a daily basis.
Now this is the problem: when I click on the links from my smartphone, they don't always open the Amazon app, but sometimes Telegram opens the page in its in-app browser. And that's a problem for me because users would never finalize a purchase by logging in again on Amazon from the Telegram browser - of course they go open the Amazon app and buy from there, and I get no commissions.
Now... is there some logic behind that? How does it work? I couldn't find a pattern for it: just sometimes it works, sometimes it doesn't. Sometimes the links open the Amazon app, sometimes they don't.
I used to shorten the links using Bit.ly, and thought it could be the problem (maybe the "amzn.to" wasn't recognized?), but nope, even using the long form links, sometimes it works and sometimes it doesn't.
Any idea?
Thank you.
Go to chat setting of Telegram and off the option to open in app link
Lets say our browser is loading a post on facebook which has an image in it. The image has been stored in CDN(Content delivery network) by Facebook and its URL is given to the browser (eg: https://scontent-bom1-2.xx.fbcdn.net/v/t1.0-9/149815846_4027009347343846_8048150791219282631_o.jpg?_nc_cat=109&ccb=3&_nc_sid=730e14&_nc_ohc=UcXY9DrL1DAAX8VQrTs&_nc_ht=scontent-bom1-2.xx&oh=da366f4d686fe03dc83123b35d21ac77&oe=604C5818)
Now, how does the browser connect to the nearest CDN server so that the image is loaded quickly?
Akamai has a good blog post that explains this.
https://blogs.akamai.com/2013/03/intelligent-user-mapping-in-the-cloud.html
I was looking at the network request/response made by photos.google.com. When I clicked on an album, as expected, the server just returned a list of photo IDs in the album and the cdn url to download the photos. Then my browser made another request(s) to Google CDN using the urls returned earlier and downloaded the photos.
The CDN url looked something like (intentionally modified to post here):
https://lh3.googleusercontent.com/rpFgzMwheqshfkwelrklsjfkwejjlfjlsjfjsfjweojjsf
When I pasted the url in browser, it was able to download the photo even when I was not signed in.
So how does Google does access control at the CDN level? Does that mean I can access any photo of anyone if I know the random key at the end (I understand it's impossible to guess because it's a really really long random string)? How does Google generate this really long random url for each resource and maintain the mapping?
Assuming you're asking about user profile pictures, yes they can access them. Google has an official API for this.
Is it possible to access a mobile users phone contacts from a web page? The company I work for would like to use QR codes to direct people to a coupon on their website and then give viewers the option of sending the url to their friends in a text message.
Obviously this would be an opt in service. Perhaps you would need to build a mobile application to accomplish the task? If anyone has an idea on how to accomplish this or something similar please let me know.
As far as I know, it is not possible to access the contact database via a web page, on any of the major platforms; in order to access this data, a native application is required.
Nate is right.
The only thing that you can do (that won't accomplish everything you need) is encode SMS message in QR code (e.g. "sms:number:subject" see http://code.google.com/p/zxing/wiki/BarcodeContents), this way your company will get user's phone number as part of SMS message, but not numbers of his/her friends.
An API for accessing contacts is being built into the WebApi by Mozilla but as of today it's not enabled by default and I expect cross browser support is still far off.