Sometimes missing single or multiple Contacts when fetching a Folder of Contacts
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
Start from the reporter's snippet, which pages through contacts() with top=100 and a PageIterator whose processPageItemCallback adds each contact to a list, then compares that list with the contacts().count() value. Reproducing the bug needs a user whose contact folder misses items, so the first step is to log which contact IDs are returned on each page and find where the gap appears. Done means a reproducible case that explains the dropped contacts, or a clear finding about the paging or serialization path in the SDK.
索引モデルが issue の本文から書いたものです。
説明
I have written a Module, that should import the Exchange Contacts from Office365 directly in the PBX's addressbook.
This has been working for a long time.
But from time to time i get a report about a missing contact, that exists in the Office365 Contact folder.
What i do exactly:
I use the MS Graph to fetch the Contacts, and dump them into a .csv file, before importing it into the pbx.
Those missing contacts don't show in the .CSV dump, which means that the contacts wasn't fetched or wasn't written due to some odd reason.
But if i check the Office365, the contact is there.
- If i trigger the script to fetch all contacts again, the contact still doesn't show up in my csv
- If i copy the original, missing contact, and trigger the script, the copy shows up in the .csv if i delete the copy the original still won't show up in the .csv if i trigger it again.
- If i update the existing contact by for example adding "Test" to their name, and save, and trigger the script, the contact shows up in the .csv
I use the following code to fetch the contacts:
O365Provider O365P = new O365Provider(TenantID, ClientID, ClientSecret, Scopes, log); //Wrapper for the GraphServiceClient with my custom logger
GraphServiceClient GSC = O365P.getGSC();
User U = GSC.users().byUserId(UserIDorUPN).get();
Integer Amount = GSC.users().byUserId(U.getId()).contacts().count().get();
log.debug("Amount in Folder: " + Amount);
List<Contact> Contacts = new ArrayList<Contact>();
ContactCollectionResponse Request= GSC.users().byUserId(U.getId()).contacts().get(requestConfiguration -> {
requestConfiguration.queryParameters.top = 100; //Pagination of 100
});
// This Code is based on the MS example: https://learn.microsoft.com/en-us/graph/sdks/paging?tabs=java
PageIterator<Contact, ContactCollectionResponse> pageIterator = new PageIterator.Builder<Contact, ContactCollectionResponse>()
.client(GSC)
.collectionPage(Request)
.collectionPageFactory(ContactCollectionResponse::createFromDiscriminatorValue)
.requestConfigurator( requestInfo -> {
requestInfo.addQueryParameter("%24top", 100);
return requestInfo;
})
.processPageItemCallback( contact -> {
Contacts.add(contact);
return true;
}).build();
pageIterator.iterate();
log.debug("Fetched: " + Contacts.size() +" Contacts");
Now the thing is, most of the time these contacts aren't new, most of them have been existing for a while in the office365 contacts, or even have been migrated there from old exchange servers. In one case i had a newly created contact show the exact issue for a customer.
I cannot pinpoint the source of this issue.
I might have tought the pagination might be wrong, but i created a Test folder with 2'133 Contacts, and all of them have been dumped to the .csv successfully using this code.
[2026-10-09T13:43:57,859] [DEBUG] [] [] [O365 Connector MSGraph] Scopes: [https://graph.microsoft.com/.default]
[2026-10-09T13:43:57,859] [DEBUG] [] [] [O365 Connector MSGraph] Setting Up Provider...
[2026-10-09T13:43:57,859] [DEBUG] [] [] [O365 Connector MSGraph] Looking for: [[email protected]]
[2026-10-09T13:43:58,098] [DEBUG] [] [] [O365 Connector MSGraph] [[email protected]] found!
[2026-10-09T13:43:58,189] [DEBUG] [] [] [O365 Connector MSGraph] Amount in Folder: 2133
[2026-10-09T13:43:59,791] [DEBUG] [] [] [O365 Connector MSGraph] Fetched: 2133 Contacts
[2026-10-09T13:43:59,838] [DEBUG] [] [] [O365 Connector MSGraph] Writing: 2133 Contacts to File: [/path/to/csv.csv]
[2026-10-09T13:43:59,838] [DEBUG] [] [] [O365 Connector MSGraph] Writing Header
[2026-10-09T13:43:59,858] [DEBUG] [] [] [O365 Connector MSGraph] Done Writing
I'm at a loss how to go about this, and can't find anything useful about this isuse.
Any ideas how to go about this?
//edit: I think it's actually close or the same issue as this: https://stackoverflow.com/questions/70374893/loading-all-contacts-using-the-microsoft-graph-api-sometimes-looses-skips-pages
Sincerely
Fabian95qw
- 主要言語
- Java
- スター
- 446
- フォーク
- 155
- 平均マージ
- 1時間 19分
- マージ済み PR(30日)
- 4
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
microsoftgraph/msgraph-sdk-java のほかの issue
-
status:waiting-for-triage type:bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
microsoftgraph/msgraph-sdk-java#2610 ·
メンテナーはふだん 1 日以内に返信
-
status:waiting-for-triage type:bug
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
microsoftgraph/msgraph-sdk-java#2656 ·
メンテナーはふだん 1 日以内に返信
-
status:waiting-for-triage type:bug
難易度 4/5 3〜5日 初心者へのやさしさ 38/100
microsoftgraph/msgraph-sdk-java#2654 ·
メンテナーはふだん 1 日以内に返信
-
status:waiting-for-triage
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
microsoftgraph/msgraph-sdk-java#2639 ·
メンテナーはふだん 1 日以内に返信
-
status:waiting-for-triage type:bug
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
microsoftgraph/msgraph-sdk-java#2589 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
microsoftgraph/msgraph-sdk-java の issue をすべて見る
似ている issue
-
area/kotlin
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
Large page[number] overflows the computed offset and returns the wrong page対応中かも @auraseb が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100