Can runApp() but cannot publish app to connect, getting Error 404

Open
#73 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, r

Research direction

Start by reproducing the runApp() flow, the redirect URI authentication, and the attempted publish to Connect described in the issue. Trace where publishing handles authentication and the redirect URI, then determine what produces the 404 and why credentials are not requested. Done means the publishing flow reaches Connect successfully and handles authentication as expected.

Written by the indexing model from the issue text.

Description

I have been able to run my shiny app without issue. The redirect URI I am using is where I hope to deploy the app to connect. When I open it in the browser I can authenticate and see my output, however, when I try to publish it I just get error 404 on Connect and it also doesn't ask me to authenticate. I would expect a pop-up or something to cache the credentials for publishing, am I missing a step here?

Dominant language
R
Stars
48
Forks
23
Avg merge
4h 2m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

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

More from Azure/AzureAuth

All issues in Azure/AzureAuth

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.