Fixed
Status Update
No update yet.
Comments
vs...@google.com
The G-suite documentation[1] provides this information, but I have submitted a feature request to make it clear on the Cloud DNS public documentation and the Cloud Console. However, I can't provide you with an ETA or guarantee the implementation of this feature, but rest assured that Google strives on improving its products and that your feedback helps us do just that.
Any future updates to this feature will be posted here.
[1]https://support.google.com/a/answer/173535
Any future updates to this feature will be posted here.
[1]
th...@gmail.com
Any updates on this?
vs...@google.com
Ditto. This is a frustrating one.
th...@gmail.com
This hit me too. At the very least, the error message returned by the API could explain what is wrong: that the string can't be longer than 255 characters.
th...@gmail.com
This is indeed extremely frustrating.
vs...@google.com
Cloud DNS upon emitting multiple TXT lines seems to re-order them. Even if you managed to enter a TXT record using multiple lines, this will render the entry unusable.
For example, this won't be recognized as a valid DKIM entry:
"DNDIed6Ys/R3J2QzhK/sEnJ+K/K4uD1yIuvK/6tzcgGcSKKFJ9Ffr/1x44eXjLXsfy9n8evvljnWwFe/U2tAtUuK7olU3CXWZGbNir5gwBbU8gE1UuVLqeW8xJgk+fj6+SMTXejvGpvcy4dsHtHNLSwIDAQAB"
"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjOLvrcvHRt8Uzqmq94BEYYyuqziuMcQCG7xIMdm/AMOmpwec6xI0craHP/9g4pfdpgiTzFgYXaAu/Y9bKomEj1dRsmvSkOEX17p89h0w5yLxEru7MsLhdVJ26JvnQeSWY/aet5nOqhH15DrjTfETGenHYDXt/sE80sfkkDdyRUuGZyC92odpMaaE6fwkxXa"
… which makes it quite severe.
For example, this won't be recognized as a valid DKIM entry:
"DNDIed6Ys/R3J2QzhK/sEnJ+K/K4uD1yIuvK/6tzcgGcSKKFJ9Ffr/1x44eXjLXsfy9n8evvljnWwFe/U2tAtUuK7olU3CXWZGbNir5gwBbU8gE1UuVLqeW8xJgk+fj6+SMTXejvGpvcy4dsHtHNLSwIDAQAB"
"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjOLvrcvHRt8Uzqmq94BEYYyuqziuMcQCG7xIMdm/AMOmpwec6xI0craHP/9g4pfdpgiTzFgYXaAu/Y9bKomEj1dRsmvSkOEX17p89h0w5yLxEru7MsLhdVJ26JvnQeSWY/aet5nOqhH15DrjTfETGenHYDXt/sE80sfkkDdyRUuGZyC92odpMaaE6fwkxXa"
… which makes it quite severe.
vs...@google.com
Same happened to me, the entries are reordered and unsable:
text = "5IL88bqDLXC3TLufrcfR4TztNLb5gSGWIPK6adGCI/sppQYiF+D1lCNtefspmFoWps8j2QpRWOyLdOMhn56jjsiew8hSDz"
text = "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlySp/8voQMhWUc2KxPzGs71ZxdS2y3DfCG1MOW52G7iQXnwXaERk127YEAgeS6KYTc14u+"
text = "TmW4/ZuYfvToBMSlLkg40JLtoLQtlP2QBoPm9VEkTBLDv84u2Bsp8ycSe02WVxscgoMsyfM0WIiD+cBlYJKFvAX82bCZgdILVfM7nzxJ9EFbdKDusRU+Wf3dSRp9TGp/i5opckxVR47UJn0mvkmzU5wHtyVjQSBnpERcmWvqHg+f7HYgxwIDAQAB"
text = "5IL88bqDLXC3TLufrcfR4TztNLb5gSGWIPK6adGCI/sppQYiF+D1lCNtefspmFoWps8j2QpRWOyLdOMhn56jjsiew8hSDz"
text = "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlySp/8voQMhWUc2KxPzGs71ZxdS2y3DfCG1MOW52G7iQXnwXaERk127YEAgeS6KYTc14u+"
text = "TmW4/ZuYfvToBMSlLkg40JLtoLQtlP2QBoPm9VEkTBLDv84u2Bsp8ycSe02WVxscgoMsyfM0WIiD+cBlYJKFvAX82bCZgdILVfM7nzxJ9EFbdKDusRU+Wf3dSRp9TGp/i5opckxVR47UJn0mvkmzU5wHtyVjQSBnpERcmWvqHg+f7HYgxwIDAQAB"
je...@google.com
Just a quick comment reply to #7 and #8 -
The string should be entered on one line (or in one box in the Cloud DNS UI), like:
"v=DKIM1;..." "continuedstring..."
This should work properly.
By adding the two items on separate lines, you're creating two different records. This will not work.
The string should be entered on one line (or in one box in the Cloud DNS UI), like:
"v=DKIM1;..." "continuedstring..."
This should work properly.
By adding the two items on separate lines, you're creating two different records. This will not work.
pa...@gmail.com
Came here to report the same thing, the suggestion in #9 worked ... place a space at the right place and the final record will split the values in the same record when stored.
je...@google.com
But the message around this is *really* stunningly unclear. I'd expect this action to be automatically applied, and then a notice displayed for dkim (if anything at all).
hi...@gmail.com
No version of this works. Following instructions as stated above only results in no action at all when the "create" button is pushed. Using the command line version fails the same way, no matter what. WHAT THE FUCK? NOT OK.
ha...@gmail.com
1. The whole string needs to be quoted
2. When you add a space, create a second quoted text string: "..." "..."
3. SHAME ON YOU GOOGLE. SHAME ON YOU.
2. When you add a space, create a second quoted text string: "..." "..."
3. SHAME ON YOU GOOGLE. SHAME ON YOU.
bl...@gmail.com
I put the DKIM into notepad so I could see the character number and the 244th character I added the whitespace with quotes like #14 suggested (e.g. mEjf" "ngD).
bl...@gmail.com
May 16, 2017: "... but rest assured that Google strives on improving its products and that your feedback helps us do just that."
It has been over 3 years - what is the status with this most basic of issues?
You can see from public fora that this issue has already wasted many minutes and hours of Googles paying customers valued time...
It has been over 3 years - what is the status with this most basic of issues?
You can see from public fora that this issue has already wasted many minutes and hours of Googles paying customers valued time...
eu...@gmail.com
This is such an obvious problem that should have been fixed by now. Seriously, what is the hold up? There are hundreds of articles and DKIM splitting utilities to work around this, it is the highest voted issue tagged with 'google-cloud-dns' on stackoverflow.com the but it's very annoying and for a layperson it's highly confusing. It can't be that hard to fix this. Grab one of your highly paid devs, sit them in front of a computer, and have them knock it out.
WHY ARE YOU IGNORING THIS?
an...@gmail.com
Hi all,
A former colleague, who now works with an "invite-only" Google Special Dev team, asked me to take a look at this Issue and and try to close this for everyone; you and Google.
If you did not earn a degree in IT, Computer Science, etc...; It would really help a lot if we just "READ THROUGH THE DESCRIPTION" carefully. Google is not "IGNORING" this, it is just that this SHOULD NOT be an ISSUE at all...
Let me point you to the right direction and "YOU" figure out the rest, I am sure you will
In the attached file, I highlighted the obvious "HINTS"... but hey,,,, the point is to CLOSE this once and for all, so here GOES...
/***---the following information will justify why this should not be an ISSUE in the first place---***/
1. Go tohttps://cloud.google.com/ and go to "Products"
2. Under "Networking", select "CLOUD DNS"
3. On the "CLOUD DNS" page, select "DOCUMENTATION" on the "SECTION" list
4. On the "DOCUMENTATION" section, select "HOW-TO GUIDES" and this will redirect you to the "ALL HOW-TO GUIDES" for "CLOUD DNS"
5. Under "MANAGING CLOUD DNS" section, select "MANAGING RECORDS"
6. From the "TABLE OF CONTENTS", select "DETAILS ON SELECTING RESOURCE RECORD TYPES" /***here is a direct link:https://cloud.google.com/dns/docs/records#record_type ***/
/***end***/
Reviewing the steps above, if this is not enough, "PLEASE" "HIRE" "AN" "EXPERT"
Q1: Which among all the DNS record types includes a "Sample Code"?
Q2: Is there not a link for TXT record that points to IETF site?
Q3: In reference to the link available on the "TXT" record, when clicked, does it not open directly section 3.1.3 of RFC 4408?
Hope this helps....
A former colleague, who now works with an "invite-only" Google Special Dev team, asked me to take a look at this Issue and and try to close this for everyone; you and Google.
If you did not earn a degree in IT, Computer Science, etc...; It would really help a lot if we just "READ THROUGH THE DESCRIPTION" carefully. Google is not "IGNORING" this, it is just that this SHOULD NOT be an ISSUE at all...
Let me point you to the right direction and "YOU" figure out the rest, I am sure you will
In the attached file, I highlighted the obvious "HINTS"... but hey,,,, the point is to CLOSE this once and for all, so here GOES...
/***---the following information will justify why this should not be an ISSUE in the first place---***/
1. Go to
2. Under "Networking", select "CLOUD DNS"
3. On the "CLOUD DNS" page, select "DOCUMENTATION" on the "SECTION" list
4. On the "DOCUMENTATION" section, select "HOW-TO GUIDES" and this will redirect you to the "ALL HOW-TO GUIDES" for "CLOUD DNS"
5. Under "MANAGING CLOUD DNS" section, select "MANAGING RECORDS"
6. From the "TABLE OF CONTENTS", select "DETAILS ON SELECTING RESOURCE RECORD TYPES" /***here is a direct link:
/***end***/
Reviewing the steps above, if this is not enough, "PLEASE" "HIRE" "AN" "EXPERT"
Q1: Which among all the DNS record types includes a "Sample Code"?
Q2: Is there not a link for TXT record that points to IETF site?
Q3: In reference to the link available on the "TXT" record, when clicked, does it not open directly section 3.1.3 of RFC 4408?
Hope this helps....
Description
:app:connectedAndroidTestDebug
E/Device: Error during Sync: timeout.
Unable to install /Users/jenkins/workspace/test_gradle_master/android_app/app/build/outputs/apk/app-debug.apk
com.android.ddmlib.InstallException
at com.android.ddmlib.Device.installPackage(Device.java:840)
at com.android.builder.testing.ConnectedDevice.installPackage(ConnectedDevice.java:83)
at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:125)
at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:47)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.android.ddmlib.TimeoutException
at com.android.ddmlib.AdbHelper.write(AdbHelper.java:819)
at com.android.ddmlib.SyncService.doPushFile(SyncService.java:671)
at com.android.ddmlib.SyncService.pushFile(SyncService.java:380)
at com.android.ddmlib.Device.syncPackageToDevice(Device.java:1036)
at com.android.ddmlib.Device.installPackage(Device.java:831)
... 9 more
We had a similar issue with our server when we did our build using Maven. Fortunately, the maven plugin has a settings named 'adbConnectionTimeout'. Increasing the value from 5000 ms to 10 000ms solved our problem.
Would it be possible to add this setting to the gradle build as well?