mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #2903] Add Choco App not working when using Powershell 7.4 #1435
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1435
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jdr8 on GitHub (Sep 24, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2903
Description
When attempting to add a Choco app to a tenant, the app is added but shows as "may be still uploading" in the M365 admin portal and not published.
Reproducing steps:
Started uploading applications to tenants
Failed adding Application XXXXXXX. Error: The given key 'Content-Type' was not present in the dictionary.
Similar issue with Store App - however error shown was
Could not assign application to XXXXXXX. Error: { "_version": 3, "Message": "Invalid operation: app's PublishingState is not 'Published'.
This still showed the same in the tenant, where the application didn't appear to have uploaded.
What I'm doing as a workaround:
Changed settings in Azure Function App from 7.4 to 7.2
UPDATE: Store App not working on 7.2 either - and Choco app that did upload fails to deploy, even on 7.2. Will need to investigate further.
Environment data
@github-actions[bot] commented on GitHub (Sep 24, 2024):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@jdr8 commented on GitHub (Sep 24, 2024):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@github-actions[bot] commented on GitHub (Oct 4, 2024):
This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.
@github-actions[bot] commented on GitHub (Oct 18, 2024):
This issue was closed because it has been stalled for 14 days with no activity.