microsoftgraph / microsoftgraph/msgraph-sdk-php
Invalid enum value "doesNotExist" Win32LobAppFileSystemOperationType
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- PHP
- Sterne
- 669
- Forks
- 150
- Ø Merge
- 15 Std. 21 Min.
- Gemergte PRs (30 T.)
- 3
Beschreibung
Describe the bug
It seems like calling the following produces an error: (v2.31.0)
$appsResponse = $this->graphServiceClient->deviceAppManagement()->mobileApps()->get()->wait();
The Variables inside JsonParseNode.php:171 (getEnumValue) are:
$this->jsonNode = "doesNotExist"
$targetEnum = Microsoft\Graph\Generated\Models\Win32LobAppFileSystemOperationType
This call produced no error with the old version v1.111:
$apps = $this->graph->createCollectionRequest('GET', '/deviceAppManagement/mobileApps')
->setReturnType(Model\MobileApp::class)
->execute();
Stacktrace:
[2025-04-09T13:25:39+0200] [DEBUG] Exception: Invalid enum value doesNotExist
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:171
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/microsoft-graph/src/Generated/Models/Win32LobAppFileSystemRule.php:65
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:147
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:120
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:95
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:94
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/microsoft-graph/src/Generated/Models/Win32LobApp.php:61
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:147
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:120
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:95
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:94
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/microsoft-graph/src/Generated/Models/MobileAppCollectionResponse.php:35
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:147
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-serialization-json/src/JsonParseNode.php:120
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-http-guzzle/src/GuzzleRequestAdapter.php:170
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/php-http/promise/src/FulfilledPromise.php:39
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/kiota-http-guzzle/src/GuzzleRequestAdapter.php:145
[2025-04-09T13:25:39+0200] [DEBUG] /vendor/microsoft/microsoft-graph/src/Generated/DeviceAppManagement/MobileApps/MobileAppsRequestBuilder.php:194
[2025-04-09T13:25:39+0200] [DEBUG] /Mycode.php
Expected behavior
No error, enum exists, idk
How to reproduce
$appsResponse = $this->graphServiceClient->deviceAppManagement()->mobileApps()->get()->wait();
The Variables inside JsonParseNode.php:171 (getEnumValue) are:
$this->jsonNode = "doesNotExist"
$targetEnum = Microsoft\Graph\Generated\Models\Win32LobAppFileSystemOperationType
SDK Version
v2.31.0
Latest version known to work for scenario above?
v1.111.0
Known Workarounds
Add the enum into the class inside vendor folder via composer patch:
"extra": {
"patches": {
"microsoft/microsoft-graph": [
"patches/microsoft-graph-Win32Lob.patch"
]
}
},
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Reproduziere den Aufruf mobileApps()->get() auf SDK v2.31.0 und beginne mit JsonParseNode.php:171 und Generated/Models/Win32LobAppFileSystemRule.php:65. Vergleiche die Definition von Win32LobAppFileSystemOperationType mit dem bereitgestellten microsoft-graph-Win32Lob.patch und dem Verhalten von v1.111. Erledigt ist die Aufgabe, wenn die Collection-Antwort den Wert doesNotExist ohne die gemeldete invalid-enum-Exception parst.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- php
- Bereich
- api
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100