Customer-Supplied Encryption Key feature is not available (but it is!) - google-cloud-storage

Not had a problem using the Customer-Supplied Encryption Key feature until today, when trying to access some stored files this error keeps appearing, even though it is supported in the UK and has been working perfectly fine for the past 18 months until now.
Am using the service via the Firebase Spark Plan so cannot ask Google for help directly, so just wondering if anyone else is having an issue?

Regarding the circumstances you described I advise you even if you don't have enough support level to open a ticket to our support platform, you can create a private issue tracker here specifying your Google Cloud Project Number and the link to this Stackoverflow question. If you follow this process, I'll be able to get this case, because I'm sure that we will need to perform some actions on your project to investigate deeper the root cause.

Related

How can use Github for my developer to work on my backend without having to share to much credentials and code?

I have a Node.js backend running on an EC2 Instance with a Mongo DB.
I need to make some changes to my iOS App along with the Backend. I have already shared the Frontend Source Code with the developer, but I don't want to share the backend (if I don't have to directly..)
I have come across Github but I am totally new to it - also I am not a developer myself.
How can I use it for my purpose? Also, can 2 developers - say iOS developer and android developer then work on the code at the same time, without causing any mess?
What would you suggest me to do?
Appreciate any help! Thank you
Android and iOS developer can work together it will not cause any issue.
Now coming to your question first of all why a frontend developer needs to look at the backend code?..
If it's necessary ask them particularly what they wants to know may be backend code documentation can help or if the guy just need a look at some specific thing you can use some remote softwares like TeamViewer or else you don't have any options he have to look at code you can use last option to ask him sign the NDA (Non Disclosure Agreement)

Google Fit Rest Api Step Counts inconsistent and different from Fit App

This seems to be a common enough problem that there are a lot of entries when one googles for help but nothing has helped me yet.
I am finding that the results provided by the REST API for estimated_steps are wildly different from those that appear in the device app.
I am running a fetch task for users via cron job on a PHP/Laravel app.
I'm using this https://developers.google.com/fit/scenarios/read-daily-step-total - estimated_steps to retrieve the step count.
Some days the data is correct. Some days its wildly different. For instance, on one given day, the REST API gives step count of 5661 while the app shows 11,108. Then there are six seven days when the stream is correct.
Has anyone faced this sort of behavior? I've tested for timezone differences, logged and analyzed the response json to see if i'm making some obvious mistake, but nope.
You may check this How do I get the same step count as the Google Fit app? documentation. Be noted that even when using the right data source, your step count may still be different from that of the Google Fit app.
This could be due to one of the following reasons:
On Wear, the Fit MicroApp when connected will display step counts queried on the phone and transferred over via the Wearable APIs. Other MicroApps accessing local-only data will only get watch steps. We are working on making this easier for developers.
Sometimes the step calculation code for the Google Fit app is updated with bug fixes before we are able to release the fixes to developers (which requires a Google Play Services release). We are also working on making it possible for developers to access fixes at the same time.
The Fit app uses a specific data source for steps and it adds some functionality (which can be seen on the documentation) on top of the default merged steps stream.
You can access the "estimated" steps stream as shown here:
derived:com.google.step_count.delta:com.google.android.gms:estimated_steps
Hope this helps!

Sending automated emails from Firebase through Google Cloud Platform (no third parties)

We've been doing some research for many hours already.
The first solution that appears everywhere (other StackExchange questions too) is using third-party service SendGrid.com and sometimes in conjunction with Zapier, but that's not the approach we are wanting to implement.
For sending without third-parties in the middle, the first solution that seemed viable was "Firebase Triggers", which was anounced on Google I/O 2014 but never came to life and seemingly was merged into Google Cloud Functions which is still in Alpha.
I'm pretty sure I had seen the solution almost a year ago in a link on the FireBase blog, but the only post that seems to have existed upon that matter is now empty.
We've never worked before with GCP, but our logic tells us this matter should be solved (inside Google) using with another GCP existing API, and the Mail API is apparently the correct one, but there seems not to be any way our Firebase Web App could make the request.
Could anyone (preferably with GCP experience) please explain what's the situation here, and how does Google expects it's FireBase developers to send emails to their clients?
Firebase Functions
As gracefully stated by #ajostergaard, TODAY Google has announced its much waited Google Cloud Functions, but precisely for Firebase they've implemented their own specific Firebase Functions which substitutes the Triggers shown in conferences since Nov. 2014 (more than 2 years ago!) and mentioned in Firebase groups .
This is an example link that explains exactly how to do what is asked in this question:
Sending emails from Firebase (FINALLY! and just in time for our WebApp)

Are there reports of Google Cloud Print usage?

I have a shared printer that is accessible to Google Cloud Print services. I would like to enable this usage for our users, however, I need to be able to run reports to see who printed what, when. We allocate printer supply costs based on usage, and as far as I can tell, Google doesn't give me a way to get any data about past print jobs other than the name of a job, it's status, and when it happened. What about who did it? I know that Google knows their email address! What about how many pages it was, or what settings were used (b/w vs. color, 1- vs. 2-sided, etc).
I hope I am just missing it.
Also, if perhaps this information is not available through Google's UI but is available through any developer-aimed APIs, that would be great info, because I can certainly get at it from that angle if necessary.
Any help or advice would be great!
I used a different approach then your. I used as a base this library https://github.com/escube/GoogleCloudSpooler i developed and created a web service from it. People can login in my system, upload the file to my server and i log everything there. My service upload to google cloud printer. This is the only way to keep control on how and what peole use my printers.
I should clean my web code in the next code and maybe publish on git hub if someone thinks that can be useful.

GAPI Class, Google Analytics API

I am about to start a new project in the Google Analytics API & PHP.
I read that Google Analytics will be deprecating XML v2.3 and v2.4 and in 6 months time, so aparently you will only be able to use v3 and retrieve information in JSON format.
http://analytics.blogspot.com/2011/12/introducing-google-analytics-core.html
My question is the following: Does this means that GAPI class won't work any longer? Anyone who has used this class before can help me answering this question ??
http://code.google.com/p/google-api-php-client/
In that case, any alternative suggestions of PHP classes that do the same thing.
Thanks so much
I've been using GAPI for a while now. And I can say with some confidence that yes it will break, if not due to XML it will be due to some other change google makes.
Having said that GAPI is the best solution I have found out there for php. It does break every 6 months to a year, usually needs one or two lines changing to fix. But GAPI is pretty popular so at least you know when your clients are calling saying analytics is throwing errors at them, you wont be the only dev tearing your hair out.
9 times out of 10, by the time I've got a problem someone else has found the fix - which is nice.
There are a few other php options out there but GAPI seems to be the most popular (usually the best way to go imho)
My approach is to build an analytics summary in the dashboard and provide a link to google analytics underneath so clients can see the full data or go there when GAPI breaks. I have been putting all my sites on the same modular system for a while now. I keep GAPI as a library in my admin layout module, this means I can make the fix once and roll it out to all my sites without too much drama.
In summary, use it but expect it to break - that way you wont be disappointed when it does.