[Bug]: "oauthFlows" does not exists

Open Beginner friendly

#2,976 opened on Sep 8, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 78/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: nodejs, typescript
Domain: api, authentication

Research direction

Start with examples/oauth/src/index.ts and its package.json, then install the pinned SDK dependencies and run the example's build or type check. Compare the AppOptions and App type declarations used by SDK version 2.0.16 with the example's oauthFlows and getOAuthFlow references; done means the cloned OAuth example builds without these TypeScript errors.

Written by the indexing model from the issue text.

Description

bug

Bug Description

I cloned this example https://github.com/microsoft/teams.ts/tree/main/examples/oauth

I am getting error for

oauthFlows
https://github.com/microsoft/teams.ts/blob/223616812417037cf8e105d49849c9207ce2e7dc/examples/oauth/src/index.ts#L10
Error: Object literal may only specify known properties, and 'oauthFlows' does not exist in type 'AppOptions<IPlugin<{}, {}>>'.

app.getOAuthFlow
https://github.com/microsoft/teams.ts/blob/223616812417037cf8e105d49849c9207ce2e7dc/examples/oauth/src/index.ts#L17
Error: Property 'getOAuthFlow' does not exist on type 'App<IPlugin<{}, {}>>'.

package.json

"dependencies": {
    "@microsoft/teams.apps": "*",
    "@microsoft/teams.common": "*",
    "@microsoft/teams.graph": "*",
    "@microsoft/teams.graph-endpoints": "*"
  },

NodeJS 24.18.0

Steps to Reproduce

Clone https://github.com/microsoft/teams.ts/tree/main/examples/oauth
NPM Install
Review the error

Expected Behavior

Successfully build the cloned example https://github.com/microsoft/teams.ts/tree/main/examples/oauth

Actual Behavior

I am getting error for

SDK Version

2.0.16

Languages Affected

TypeScript

Dominant language: TypeScript
Stars: 729
Forks: 270
Avg merge: 2d 4h
Merged PRs (30d): 19

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Puppeteer] Remove deprecated `getElementXY` helper and update usage Open

calcite-components needs triage refactor

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Esri/calcite-design-system#15203 · Opened Sep 21, 2026
Locale guard misses en_GB, so a removed key can survive in a shipped bundle Open

Difficulty 2/5 1-3 hours Newbie friendliness 91/100

0xMiden/wallet#1078 · Opened Sep 21, 2026
[good first issue] 🍘 Add new Trivia Question 535 (good-first-issue) Open

community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs

Difficulty 1/5 Under an hour Newbie friendliness 95/100

lingdojo/kana-dojo#30695 · 1 comment · 5 reactions · Opened Sep 21, 2026
Daemon passes --experimental-wasm-jspi unconditionally on Node >= 24; Node 26 rejects the flag Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

Automattic/studio#4908 · Opened Sep 21, 2026
`polar.normalize` - missing r = 0 guard Open

Difficulty 2/5 1-3 hours Newbie friendliness 90/100

pmndrs/math#58 · Opened Sep 21, 2026

More TypeScript issues