[GH-ISSUE #2394] Publishing choco apps does not work #1220

New issue

Closed

opened 2026-03-02 13:42:29 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 13:42:29 +03:00

Owner

Originally created by @markkoele on GitHub (May 2, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2394

Description

Als er een choco app in de queue wordt gezet wordt deze niet gepubliceerd naar intune/mdm. niet handmatig en niet na 48 uur.

When a choco app is placed in the queue, it is not published to intune/mdm. not manual and not after 48 hours.

Environment data

Sponsored instance 
Front end version number: 5.6.1
Back end version number: 5.6.2
Tried Tenant Cache Clear: true
Tried Token Cache Clear: true

Originally created by @markkoele on GitHub (May 2, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2394 ### Description Als er een choco app in de queue wordt gezet wordt deze niet gepubliceerd naar intune/mdm. niet handmatig en niet na 48 uur. When a choco app is placed in the queue, it is not published to intune/mdm. not manual and not after 48 hours. ### Environment data ```PowerShell Sponsored instance Front end version number: 5.6.1 Back end version number: 5.6.2 Tried Tenant Cache Clear: true Tried Token Cache Clear: true ```

kerem

2026-03-02 13:42:29 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 13:42:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 2, 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!".

@github-actions[bot] commented on GitHub (May 2, 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!".

kerem commented

2026-03-02 13:42:30 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (May 2, 2024):

This isn't the place for support, if you're a sponsor you can contact the support address.

@KelvinTegelaar commented on GitHub (May 2, 2024): This isn't the place for support, if you're a sponsor you can contact the support address.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#1220

No description provided.

Rows
Columns