DocumentApp.getActiveDocument().getId() throws error for Word/docx files [235693509]

Duplicate

of 319035101

Bug

Status Update

No update yet.

Description

pa...@section6.nz

created issue #1

Jun 13, 2022 03:46AM

A short description of the issue:

In a Document (Docs) Google Workspace Editor Add-On

var id = DocumentApp.getActiveDocument().getId();

Throws the following error when the active document is a non-google Doc. Specifically, a Microsoft Word document or .docx.

Exception: The document is inaccessible. Please try again later.

What steps will reproduce the problem?

Build an add-on that has a mainfest that includes

  "addOns": {
    "docs": {
      "homepageTrigger": {
        "runFunction": "onEditorHomepage_Docs",
        "enabled": true
      }
    }
   }

Code the onEditorHomepage_Docs function thus:

function onEditorHomepage_Docs(event) {
  console.log(event);
  try {
   id = DocumentApp.getActiveDocument().getId();
  }
  catch (err) {
    console.error(err);
    throw err;
  }
  ...etc...
}

Open add-on in a Document editor when the document is a .docx. file (Word Document) See log for errors.

What is the expected output? What do you see instead? If you see error messages, please provide them.

I appreciate that the functionality of what can be done with a word document is limited. However, everything my add-on wants to do still works with a .docx. if I could only get its document id. (I tested it with a hard-coded copy of the .docx. id).

But there is nowhere in the interface to get the ID. It is not present in the event and obviously not from the API call.

Thank you.

Comments

co...@google.com <co...@google.com> Jun 13, 2022 07:01AM

Assigned to co...@google.com.

pa...@section6.nz <pa...@section6.nz> #2Jun 13, 2022 09:07AM

The flow of the wizard is really meant for the key to be used for signing. In fact, if you want to just create a key for code transparency you have to start a flow (signing an APK/Bundle) and then back out of it/cancel after you created the key.

To properly support this, we should also allow you to start a wizard that is just creating a key, and nothing else.

co...@google.com <co...@google.com> #3Jun 13, 2022 01:22PM

Thanks for this feature request. The "Generate Signed Bundle / APK" flow is only meant to generate keys for APK or AAB signing. We'll plan to add a warning to the flow to clarify that.

pa...@section6.nz <pa...@section6.nz> #4Jun 13, 2022 11:02PM

Hi
Your answer fails to acknowledge that DocumentsApp and SlidesApp behave one way and SpreadsheetApp another. One of the ways must be "wrong".

The DriveApp, as you note, works with the target file types. But through the Editor add-on API, there is no way to know the active document (unless it's a spreadsheet via SpreadsheetApp). So it does not follow that DriveApp is a solution in this case—what id do we pass to DriveApp.getFileByID(?).

Not to mention that an exception that says "...try again later" is also just WRONG. Unless "later" means when this bug is resolved.

Thank you.

Message last modified on Jun 14, 2022 08:06PM

co...@google.com <co...@google.com> #5Jun 24, 2022 04:06PM

Status: Won't Fix (Intended Behavior)

Hi,

The documentation states that only Google Products are supported. The fact that excel spreadsheets are supported is an edge case and it is not encouraged.

DriveApp.getFileById() will let you fetch any file stored in Google Drive, which you can then manipulate as you see fit (and easily convert into Google Products if needed).

As this is working as intended, I will be closing this case.

Thanks!

pa...@section6.nz <pa...@section6.nz> #6Sep 14, 2022 03:52AM

I am really disappointed that you did not take the time to understand this issue correctly. Again, DrivApp.getFileById is not available to use in this case—the ID is not provided to that function in the event JSON information. Nor is it available through any of the other APIs in this context (especially because DocumentApp.getActiveDocument() fails). So there is no workaround in the case you want to work with a non-google doc in an Editor Add-On.

The ID is available and is passed in the event JSON of onItemsSelectedTrigger. Here, DriveApp.getFileByID is useful.

If your position is that this is not supported, then I will accept that. But please do not tell me to use a solution that is simply not valid. It does you no credit and diminishes my request for support.

thank you

jp...@google.com <jp...@google.com> Jan 8, 2024 04:39PM

Status: Duplicate of

319035101