probot: probot: Invalid app_id `ID number`

Bug Report

Current Behavior Everytime I do check run update, I get probot: Invalid app_id ID`

  05:30:29.401Z ERROR probot: Invalid app_id `ID`
  HttpError: Invalid app_id `ID`
      at response.text.then.message (/my-probot-app/node_modules/@octokit/request/dist-node/index.js:66:23)
      at <anonymous>
      at process._tickDomainCallback (internal/process/next_tick.js:228:7)

Expected behavior/code I am able to create a check run without any problem.

Is there something I am missing here ?

Environment

Probot version(s): [e.g. v6.0.0]
Node/npm version: [e.g. Node 8/npm 5]
OS: [e.g. OSX 10.13.4, Windows 10]

Possible Solution

Additional context/Screenshots Add any other context about the problem here. If applicable, add screenshots to help explain.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 40 (18 by maintainers)

Most upvoted comments

@gr2m Ok thanks for all your answers, that helped a lot! For those who won’t read everything except the last post, a GitHub App has rights on the checkrun that it owns, so the ones it created… The checksuites that are automatically created (on pull_request for example) are “owned” by the App github-actions, as which you cannot authenticate, so no possibility to update a checksuite/checkrun this way, you would need to create it yourself in your own CI server I guess.

marcgspc on Jan 20, 2020

There is no restriction other then the permissions the installation has. But if the permissions were insufficient, the error message would be different.

GitHub had their yearly conference last week so everyone was very busy, I’m sure they will get back to you soon

gr2m on Nov 17, 2019

Hmm I’m sorry I can’t help better, maybe there is a bug somewhere in Octokit, Probot or even GitHub’s API.

I think what I would do next is to send a curl request directly from the terminal which updates a check run the way you want. If that returns the same error, then send the curl request to support@github.com, they will be able to help.

If it works with curl, then the next thing I would do is to create a minimal test case with @octokit/rest. https://runkit.com/ is great to do that, e.g. https://runkit.com/gr2m/octokit-rest-js-1319 Once we have a test case that reproduces your problem, it will be easier to debug the code

<div>RunKit is Node prototyping</div><div>RunKit notebooks are interactive javascript playgrounds connected to a complete node environment right in your browser. Every npm module pre-installed.</div>

<div>RunKit</div><div>RunKit notebooks are interactive javascript playgrounds connected to a complete node environment right in your browser. Every npm module pre-installed.</div>

gr2m on Nov 8, 2019