I am trying to approve (with Google) the app that synchronizes employees' calendars with their Gmail accounts.
It has been a difficult and long process. The last hurdle to overcome is that Google said the following:
"Inconsistent branding" - they are saying that the "sign in" Google button (see image) is the old version (apparently very old) and needs to be the new version.
This means that Amelia is using an old library.
It would take you guys exactly 10 min to update this button to the new one and it would be a lot better for all your users.
*** Can you please assist with this? And before you reply that I should add this to the improvement requests - this is a 10 min fix which if not done means that all your users can't authenticate the app. ***
Apologies, but I'm trying to understand if you are trying to approve your custom application with Google, or if you are reporting an issue with Google not being able to sync the employee calendar within Amelia because of the old button design?
We can confirm that our users are able to connect to the employee calendar without any issues regarding the button design. Certainly, it should be a case with the sync between the Amelia and Google Calendar.
It is not MY custom app. It is the App that Amelia requires that all users use in order to connect the calendars.
I’m trying to approve the app (because if I don't then all Employees see a warning message that the app is not safe - this is what all Amelia customers will see). Google Cloud responded and said that there is a branding issue because the “sign-in” button that employees see -(I sent a screenshot) is using the OLD Google branding button.
Any of your clients that will try approve the app will not succeed (even if the calendar syncing works) because Google does not approve the use of old branding.
As I mentioned, this is something that takes 10 min to fix on your side and I assume that TMS plugins and Alexander (the CEO) would want your clients to be able to approve their apps right?
Last time I reached out support said that we (Amelia users), need to approve the app ourselves. I would love to solve this myself but I can’t because only you control which button is displayed on your end and Google doesn't approve old buttons (these buttons have been disavowed by google a long time ago).
If you could please change this one little button to the ‘new’ Google button (I provided a screenshot) this would be appreciated. It shouldn't take more than 10 min.
The Google Calendar integration works in the same way as it has been for the previous couple of years, nothing has changed in terms of functionality for Amelia.
If that was the case, we would have a large number of tickets from users reporting it, which is not the case.
Our QA Team is also performing tests every day to ensure it works.
You can download a Video from this link of our latest Test we just ran today.
We used one of our Demo Websites which has Amelia 7.0 installed, and as you can see in the Video, there is just a couple of steps where Google says "The App is not verified", but your Employees can easily just press a couple of buttons to bypass this warning.
The first step, when it says "Google hasn't verified this app", the Employee needs to press "Advanced".
Then, this new section appears beneath, that says "Continue only if you understand the risks and trust the developer".
Your Employee just needs to hit this "Go to wpamelia.com ( unsafe)".
It might show this last step where it says "wpamelia.com wants additional access to your Google Account";
There the Employee can just hit "Continue" ,and that's it.
This is the same behaviour that Aleksandar has shown in our Video Tutorial of a situation when Google has not verified the App - as he says in the Video, it is perfectly safe to just proceed there and to tell Google that the Employee trusts the developer and the App.
-
But, we will still take into consideration all the details you passed to us, because in that Video we have shown that is normal when it is a newly registered App, it takes time for Google to verify it;
And it is going to work, but we can understand that you wish to get the App verified with Google to avoid having your employees to 'additionally allow the App' during their Calendar connection;
So we will share this with our Management and going to report back on the subject as soon as they advise.
Thank you for sharing all the details with us and for your patience.
Thank you for explaining. I'm really surprised that TMS plugins is OK with the fact that employees / users have to see this scary WARNING message when they connect their calendars. I assume that if TMS Plugins can do something as easy as updating the Google Logo/button (10 minutes work) which would help us (us, the PAYING customers of Amelia) then you would want to help right?
Anyway, I think the important part is this (what you wrote):
"...we can understand that you wish to get the App verified with Google to avoid having your employees to 'additionally allow the App' during their Calendar connection; So we will share this with our Management and going to report back on the subject as soon as they advise."
I will eagerly await your update regarding the change of the Google Button because without this all the Amelia users cannot approve the app.
p.s.: Kindly tell Aleksandar that I reached out to him through LinkedIn. We have a lot of mutual connections and I would be happy to discuss something things with him.
Apologies for the long wait. After investigation, we can confirm that the issue is not related to the button design. The main issue here is the verification of your application on Google Cloud and the fact that your application is not verified. The button in Amelia is only for the process of connecting the Google Calendar with employees, but it's not meant for application verification. We would suggest contacting Google Support regarding the issue of your application verification on the Google Cloud. We are sure that the synchronization will work when the application is verified on the Google Cloud.
We can also confirm that all our users who have a Google Cloud application verified, do not have any issues regarding the button design and they are able to connect the Google Calendar without any issues.
If that's not the case, we would have a lot of tickets and certainly be familiar with the fact the button design is the problem.
To be honest, I am SHOCKED by your reply? Are you saying that I am not telling the truth about the process with Google Cloud?
I have been trying for a month to verify my app and I CAN'T because YOU guys have a branding issue that we (the users) cannot change!
I am attaching screenshots of my emails with google cloud. You can EASILY see that they specifically say that you - Amelia - has a branding issue with the "sign-in" button. It is an OLD version that Google does not accept anymore! I cannot change this and none of your users can. That is why i am asking that you change the button!
If you want, I can include someone from TMS in all my emails with Google.
STOP making your users suffer for something that takes 10 minutes for you to fix. Doesn't Amelia want to have updated logos and comply with Google? Doesn't TMS want to help it's customers approve the app?? Either no one tried (because the process takes time and patience) or they gave up because of your support, or Google has changed how they review things! Either way, the evidence is clear - see their message!
Again I am asking that you please update the button. It takes 10 minutes (much shorter than all this correspondence so far).
p.s.: I have also attached the button that Google Cloud asks should be updated. I also attached the email from them.
I am shocked that instead of Amelia wanting to make itself better and help it's users, this is what you make us go through. Why? Don't you want people to use your service? Don't you want people to say how good Amelia is? This is crazy!
Sorry for the inconvenience, I've certainly escalated this to the developers, so they can give their opinion regarding this. As we stated, this is the first case that we see that the application can't be verified because of the button design. That button only serves as the trigger to make the integration between the employee and the Google Calendar, but certainly, it's not meant for app verification.
I will report back as soon as I have the feedback.
Sorry for the inconvenience again and thank you for your patience and understanding.
Please accept our apologies for the late reply. We did our best to solve this issue as fast as possible. We were able to come up with the changes, and the status now is "testing phase". As soon as this is approved, we will look forward to adding this change in the future update. Unfortunately, can't promisee ETA at this moment, but you can follow the changelog page, to keep up with the updates.
Sorry for the inconvience again and let us know if you have any other questions.
Hi
I am trying to approve (with Google) the app that synchronizes employees' calendars with their Gmail accounts.
It has been a difficult and long process. The last hurdle to overcome is that Google said the following:
"Inconsistent branding" - they are saying that the "sign in" Google button (see image) is the old version (apparently very old) and needs to be the new version.
This means that Amelia is using an old library.
It would take you guys exactly 10 min to update this button to the new one and it would be a lot better for all your users.
*** Can you please assist with this? And before you reply that I should add this to the improvement requests - this is a 10 min fix which if not done means that all your users can't authenticate the app. ***
This is the link showing that Google does not support these buttons any more: https://developers.google.com/identity/sign-in/web/build-button
Please assist.
Thanks!
Should be the white button
Attached files: New google branding sign in.jpg
Hello Assaf,
Thanks for reaching out to us.
Apologies, but I'm trying to understand if you are trying to approve your custom application with Google, or if you are reporting an issue with Google not being able to sync the employee calendar within Amelia because of the old button design?
We can confirm that our users are able to connect to the employee calendar without any issues regarding the button design. Certainly, it should be a case with the sync between the Amelia and Google Calendar.
Looking forward for your reply.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Stefan,
It is not MY custom app. It is the App that Amelia requires that all users use in order to connect the calendars.
I’m trying to approve the app (because if I don't then all Employees see a warning message that the app is not safe - this is what all Amelia customers will see). Google Cloud responded and said that there is a branding issue because the “sign-in” button that employees see -(I sent a screenshot) is using the OLD Google branding button.
Any of your clients that will try approve the app will not succeed (even if the calendar syncing works) because Google does not approve the use of old branding.
As I mentioned, this is something that takes 10 min to fix on your side and I assume that TMS plugins and Alexander (the CEO) would want your clients to be able to approve their apps right?
Last time I reached out support said that we (Amelia users), need to approve the app ourselves. I would love to solve this myself but I can’t because only you control which button is displayed on your end and Google doesn't approve old buttons (these buttons have been disavowed by google a long time ago).
If you could please change this one little button to the ‘new’ Google button (I provided a screenshot) this would be appreciated. It shouldn't take more than 10 min.
Thanks.
Hi Assaf,
The Google Calendar integration works in the same way as it has been for the previous couple of years, nothing has changed in terms of functionality for Amelia.
If that was the case, we would have a large number of tickets from users reporting it, which is not the case.
Our QA Team is also performing tests every day to ensure it works.
You can download a Video from this link of our latest Test we just ran today.
We used one of our Demo Websites which has Amelia 7.0 installed, and as you can see in the Video, there is just a couple of steps where Google says "The App is not verified", but your Employees can easily just press a couple of buttons to bypass this warning.
The first step, when it says "Google hasn't verified this app", the Employee needs to press "Advanced".
Then, this new section appears beneath, that says "Continue only if you understand the risks and trust the developer".
Your Employee just needs to hit this "Go to wpamelia.com ( unsafe)".
It might show this last step where it says "wpamelia.com wants additional access to your Google Account";
There the Employee can just hit "Continue" ,and that's it.
This is the same behaviour that Aleksandar has shown in our Video Tutorial of a situation when Google has not verified the App - as he says in the Video, it is perfectly safe to just proceed there and to tell Google that the Employee trusts the developer and the App.
-
But, we will still take into consideration all the details you passed to us, because in that Video we have shown that is normal when it is a newly registered App, it takes time for Google to verify it;
And it is going to work, but we can understand that you wish to get the App verified with Google to avoid having your employees to 'additionally allow the App' during their Calendar connection;
So we will share this with our Management and going to report back on the subject as soon as they advise.
Thank you for sharing all the details with us and for your patience.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Stefan,
Thank you for explaining.
I'm really surprised that TMS plugins is OK with the fact that employees / users have to see this scary WARNING message when they connect their calendars.
I assume that if TMS Plugins can do something as easy as updating the Google Logo/button (10 minutes work) which would help us (us, the PAYING customers of Amelia) then you would want to help right?
Anyway, I think the important part is this (what you wrote):
"...we can understand that you wish to get the App verified with Google to avoid having your employees to 'additionally allow the App' during their Calendar connection; So we will share this with our Management and going to report back on the subject as soon as they advise."
I will eagerly await your update regarding the change of the Google Button because without this all the Amelia users cannot approve the app.
p.s.: Kindly tell Aleksandar that I reached out to him through LinkedIn. We have a lot of mutual connections and I would be happy to discuss something things with him.
Thanks! 🙏🏼
Hello Assaf,
Apologies for the long wait. After investigation, we can confirm that the issue is not related to the button design. The main issue here is the verification of your application on Google Cloud and the fact that your application is not verified. The button in Amelia is only for the process of connecting the Google Calendar with employees, but it's not meant for application verification. We would suggest contacting Google Support regarding the issue of your application verification on the Google Cloud. We are sure that the synchronization will work when the application is verified on the Google Cloud.
We can also confirm that all our users who have a Google Cloud application verified, do not have any issues regarding the button design and they are able to connect the Google Calendar without any issues.
If that's not the case, we would have a lot of tickets and certainly be familiar with the fact the button design is the problem.
I hope it helps.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Dear Stefan,
To be honest, I am SHOCKED by your reply? Are you saying that I am not telling the truth about the process with Google Cloud?
I have been trying for a month to verify my app and I CAN'T because YOU guys have a branding issue that we (the users) cannot change!
I am attaching screenshots of my emails with google cloud. You can EASILY see that they specifically say that you - Amelia - has a branding issue with the "sign-in" button. It is an OLD version that Google does not accept anymore! I cannot change this and none of your users can. That is why i am asking that you change the button!
If you want, I can include someone from TMS in all my emails with Google.
STOP making your users suffer for something that takes 10 minutes for you to fix. Doesn't Amelia want to have updated logos and comply with Google? Doesn't TMS want to help it's customers approve the app?? Either no one tried (because the process takes time and patience) or they gave up because of your support, or Google has changed how they review things! Either way, the evidence is clear - see their message!
Again I am asking that you please update the button. It takes 10 minutes (much shorter than all this correspondence so far).
p.s.: I have also attached the button that Google Cloud asks should be updated. I also attached the email from them.
I am shocked that instead of Amelia wanting to make itself better and help it's users, this is what you make us go through. Why? Don't you want people to use your service? Don't you want people to say how good Amelia is? This is crazy!
Attached files: the button that Google requires.png
branding message from google 1.png
branding guidelines 3.png
branding guidelines 2.png
Hello Assaf,
Sorry for the inconvenience, I've certainly escalated this to the developers, so they can give their opinion regarding this. As we stated, this is the first case that we see that the application can't be verified because of the button design. That button only serves as the trigger to make the integration between the employee and the Google Calendar, but certainly, it's not meant for app verification.
I will report back as soon as I have the feedback.
Sorry for the inconvenience again and thank you for your patience and understanding.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hello Assaf,
Please accept our apologies for the late reply. We did our best to solve this issue as fast as possible. We were able to come up with the changes, and the status now is "testing phase". As soon as this is approved, we will look forward to adding this change in the future update. Unfortunately, can't promisee ETA at this moment, but you can follow the changelog page, to keep up with the updates.
Sorry for the inconvience again and let us know if you have any other questions.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables