An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

I'm trying to change an app's Primary Language in App Store Connect from de-DE to nl-NL and hitting a state I can't resolve through any interface available to me. Environment App Store Connect (web UI) and App Store Connect API v1 Problem UI: App Information → Primary Language → nl-NL → Save fails with: "Primary Locale couldn't be saved because you must first provide all the required screenshots for each version in this language." API: PATCH /v1/apps/1669670490 with attributes.primaryLocale = "nl-NL" returns HTTP 409: ENTITY_ERROR.ATTRIBUTE.INVALID.INVALID_STATE.MISSING_SCREENSHOTS_PRIMARY_LOCALE Error detail contains an unsubstituted placeholder: "...you must first provide all the required @@LANGUAGE_VALUE@@ screenshots..." What I've verified Current live version (3.7.6) and current editable version (3.7.11) both have complete nl-NL screenshot sets for all required device sizes (6.9" iPhone, 13" iPad). No Watch app, iMessage extension, Custom Product Pages, In-App Events, or IAPs. Enumerated all 23 versions via the API (1.0 → 4.1.0). 19 of them have an nl-NL appStoreVersionLocalization (with real historical description/keywords/support URL) but zero nl-NL screenshots attached. Tried POSTing an nl-NL screenshot set to one historical version (4.1.0) directly via the API to confirm this isn't just a UI restriction. Also returns 409 ENTITY_ERROR.ATTRIBUTE.INVALID.INVALID_STATE — historical versions are locked against edits (including screenshots) at the API level, not just the UI. Question Since these historical versions can't be edited through any supported interface, is there a documented way to satisfy or bypass the "screenshots for each version" check for locked historical versions when changing Primary Locale? Filed as case 20000130035264 with Developer Support, who pointed me here for the technical side.

I am having an issue with both In-App Purchases and auto-renewable subscriptions using the current App Store Connect submission workflow. My app was previously submitted for review along with its IAPs and first auto-renewable subscriptions. The app itself was approved, but the IAPs and subscriptions were not approved with it. Afterward, the IAPs/subscriptions showed “Developer Rejected.” I did not intentionally reject these products individually. Because App Store Connect states that the first auto-renewable subscription must be submitted with a new app version, I created a new version (1.1.8), uploaded a new binary, and added version 1.1.8 for review. I now have the following situation: • My In-App Purchases show “Ready for Review.” • My subscription group shows “Ready for Review.” • Both auto-renewable subscriptions show “Ready for Review.” • The Add for Review controls for these products are disabled, so I cannot add them to another submission. • App Store Connect shows only one Draft Submission. • When I open that Draft Submission, the only item listed is iOS App 1.1.8. • None of the IAPs, the subscription group, or the individual subscriptions appear in the Draft Submission. Therefore, App Store Connect appears to consider the IAPs and subscriptions Ready for Review, but they are not actually visible in any Draft Submission and I have no way to add them to the 1.1.8 submission. I have tried removing iOS App 1.1.8 from the Draft Submission and adding it again. This does not change the status of the IAPs or subscriptions and does not make them available to add to the submission. I have contacted Apple Developer Support twice, but so far they have not been able to provide a solution. Has anyone encountered this with the new App Store Connect IAP/subscription submission workflow? Is there a way to reset the review/submission state of IAPs and subscriptions that show “Ready for Review” but are not actually present in any Draft Submission? I would strongly prefer to keep the existing product identifiers rather than recreate all of the IAPs and subscriptions.

Hi all, I hope someone from App Review can take a look My situation: QuidProQuote: Memory Keeper (app ID: 6791349683) is a simple cross-platform app where a single purchase unlocks both the macOS and iOS versions. Both versions were submitted from the same build/codebase. The problem is that while my macOS version has been approved and is now pending my release, the iOS version (submission ID: 9fba8d59-d9a7-4a09-bbbe-1d23035adbe1) has been "Waiting for Review" for 12 days now. 2026-07-30, ~4:30pm ET: Both macOS and iOS submissions entered "Waiting for Review" 2026-08-06, ~10am ET: macOS version approved, now Pending Developer Release 2026-08-11 (Today): iOS version still showing "Waiting for Review," 12 days with no status change This ends up being more than a normal wait because the purchase is shared across platforms... releasing the macOS version now would put it in front of customers without the iOS half of what they're paying for. I can't release the approved macOS build until the iOS version clears review, so the delay on one platform is effectively holding both hostage. I did file an expedited review request today (2026-08-11), received confirmation ("we'll expedite this review"). But I read advice that additionally it would be wise to register the problem here. Thanks for any visibility into this!

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

Hello, I renewed my Apple Developer Program membership on July 29, 2026. The payment was successfully processed, I received the invoice and renewal confirmation, and the Apple Developer website shows that my membership is active. For approximately one week, App Store Connect has continued to display this error: Developer Program Membership Expired Your membership has expired, and your apps have been removed from the App Store until you renew your membership. To renew, a user with the Account Holder role must sign in and renew the membership on the Apple Developer website. Because of this incorrect status, I cannot submit apps, and App Store Connect states that my existing apps have been removed from the App Store. I have contacted Apple Developer Support multiple times. I received two responses, but neither addressed the App Store Connect membership-status issue. The renewal itself is already complete; the problem appears to be a synchronization issue between the Apple Developer portal and App Store Connect. Has anyone experienced this situation? How long did synchronization take, and was there a specific support team or escalation path that resolved it? Any advice would be appreciated.

Hello, Our app was submitted on August 7 and has remained in “Waiting for Review” with no status change. This is now a launch-blocking issue for a scheduled enterprise customer rollout on August 13. Hundreds of participants are already scheduled for mobile user testing and are unable to proceed without the iOS app. We have submitted an expedited review request and contacted Developer Support, but have not received a response or any update from either channel. At this point, the App Review delay is directly blocking a committed enterprise launch and participant testing schedule. We would greatly appreciate any urgent assistance in getting this case reviewed or escalated to the appropriate App Review team. App Name: Satellica App Apple ID: 6797731123 Submission ID: b7105850-5a17-489d-907d-550febe3895a Thank you.

Our app cannot be found by its own name on the France App Store, because search silently rewrites the query. App: Kaiho: Arrêter de fumer / Kaiho: Quit Smoking Coach Apple ID: 6760356299 Feedback Assistant: FB24267557 WHAT HAPPENS Searching "Kaiho" on the France storefront returns kaiju monster games. The page reads "Affichage des résultats pour « kaiju »" ("Showing results for kaiju") with a "Rechercher « Kaiho » à la place ?" link underneath. Our app is not in the results at all. The first item served is a paid ad for an unrelated app, then KAIJU N° 8 THE GAME. THIS IS NOT A RANKING QUESTION The app is correctly indexed on that same storefront: searching "kaiho arreter de fumer" returns it as the #1 result. The substitution happens before ranking the term itself is replaced. TWO APPLE SYSTEMS DISAGREE While typing, the App Store's own autocomplete proposes "kaiho: arrêter de fumer" as its first suggestion, and offers "kaiho in Developers". After submitting, the results engine rewrites the term to "kaiju". The suggestion service and the results engine hold contradictory views of the same query. REPRODUCIBLE ACROSS STOREFRONTS The search response exposes the substitution explicitly. MZSearch with term=kaiho returns "spellCorrection": "kaiju" on X-Apple-Store-Front 143442 (France), and "kahoot" on 143459 (Switzerland), 143443 (Germany) and 143450 (Italy). Storefronts 143441 (US), 143446 (Belgium), 143455 (Canada) and 143454 (Spain) return no spell correction and do return the app. Measured 2026-08-11. WHY IT MATTERS "Kaiho" is our French trademark (No. 5255039, INPI, classes 9, 41, 42) and the only term under which we ask people to look for us. France is our home market and the source of nearly all our iOS installs. Anyone told to "search for Kaiho on the App Store" lands on monster games instead. I have filed FB24267557 and opened a Developer Support case under Distribution > App Store search and visibility. QUESTION FOR THE COMMUNITY Has anyone managed to get Apple to drop a spell correction on their own brand name? I have seen the same pattern reported for "Myseum" being corrected to "Museum" (thread #780657) with no resolution posted. If you got it fixed, what actually moved it? Feedback Assistant, a support case, Search Ads volume on the exact term, or simply time?

We are experiencing an issue when inviting a user to join our Apple Developer Program team through App Store Connect Users and Access. The purpose of adding this user is to include them as an internal TestFlight tester after the invitation is accepted. The invited user received the Apple Developer invitation email and clicked the "Accept invitation" link. The invitation link opens the following page: https://appstoreconnect.apple.com/activation_ds?key=... The page displays "Sign in to accept your invitation" and asks the user to sign in with an Apple Account. After the user signs in successfully, the page redirects back to the same sign-in page and asks the user to sign in again. The invitation cannot be accepted, and the user cannot join the Apple Developer Program team. Steps to reproduce: Go to Users and Access in App Store Connect. Add a new user and send an invitation to join the Apple Developer Program team. The invited user receives the Apple Developer invitation email. The invited user clicks the "Accept invitation" link. The page opens appstoreconnect.apple.com/activation_ds. The user signs in with an Apple Account. After signing in, the page redirects back to the same sign-in page. Repeating the sign-in process results in the same redirect loop. Expected result: The invitation should be accepted after the user signs in, and the user should be added to the Apple Developer Program team. Actual result: The page keeps redirecting back to the sign-in page, and the user cannot accept the invitation. Troubleshooting already tried: Safari and Chrome Private browsing mode Clearing browser cookies Signing out of Apple ID before opening the invitation link again Opening the link directly in the browser instead of an email app embedded browser The issue still occurs.

I have spent eight weeks trying to get this account opened, and I paid for it over six weeks ago. Roni confirmed that the escalation managers have had every piece of information they requested for weeks, but the account still has not been opened. I asked to file a complaint about the escalation managers. Roni could not tell me the name of the department that would review my complaint, nor could she explain the complaint process. After she gave me conflicting information, I said I would also like to complain about the lack of clear information; she told me she did not know Apple's complaint process at all. She then said that any complaint about her would go to a separate team. When I asked whether both complaints would go to the same team, she said she was not allowed to tell me. I have therefore paid for a service that has not been delivered, and been given no usable route to complain about either failure. An account taking 8 weeks is bad service. An advisor telling you she cannot name the reviewing department, cannot describe the process, and is not allowed to say whether two complaints go to the same team — that's a company with no functioning complaints route. Complaints are discretionary for Apple; money isn't. A paid-for service has to be performed within a reasonable time, and 6+ weeks with zero outstanding items is past it. App Store Connect isn't a convenience — it's the entire benefit of the thing I paid for. No App Store Connect means no submissions, no builds, no releases, no revenue. I haven't received partial service; I've received none of it.

Hello, My enrollment in the Apple Developer Program has been "On Hold" for over a year. I am applying for an individual account and urgently need access to complete my setup. I contacted Apple Support two weeks ago and received a single response stating they would look into it, but I have not received an update since. Any assistance or guidance from the community or forum staff on how to resolve this would be greatly appreciated. Thank you!

I've hit a state I can't get out of and support hasn't responded, so posting here in case someone from Apple can route it. developer.apple.com/account shows me only the free-account view — no Membership section, no team, no Certificates, Identifiers & Profiles, and no Renew option. It offers "Join the Apple Developer Program". But clicking Enroll lands on developer.apple.com/enroll/ineligible/account-holder: "Your Apple Account is already associated with the Account Holder of a membership." Xcode: "Unable to find a team with the given Team ID 'S25RFUK37U' to which you belong." App Store Connect still works and still lists my published apps, so the team record clearly exists. So I can't enroll (Apple says I already have a membership) and I can't renew (no membership is exposed anywhere in my account). I'm the sole Account Holder, nobody else administers the account, and I received no email about expiration or termination. Case 102945522781 has been open since July 18 with three messages sent and only automated acknowledgements in return. Has anyone seen this specific combination, and is there a way to get a Developer Account team review other than the standard contact form?

Hello, Apple’s documentation appears inconsistent about which App Store Connect API should be used to submit an Apple-hosted Background Asset version for external TestFlight review: In WWDC25 “Discover Apple-Hosted Background Assets”, Apple says that the asset pack version can be submitted using the POST /v1/betaBackgroundAssetReviewSubmissions. In Uploading and versioning Apple hosted background assets, the external beta review instructions link to “Submit an app for beta review,” which uses POST /v1/betaAppReviewSubmissions. These two resources have different behavior. betaBackgroundAssetReviewSubmissions I called the public API with the same resource structure used by the App Store Connect web UI: POST https://api.appstoreconnect.apple.com/v1/betaBackgroundAssetReviewSubmissions { "data": { "type": "betaBackgroundAssetReviewSubmissions", "relationships": { "backgroundAssetVersion": { "data": { "type": "backgroundAssetVersions", "id": "<BACKGROUND_ASSET_VERSION_ID>" } } } } } The public API returned 404 PATH_ERROR: The resource 'v1/betaBackgroundAssetReviewSubmissions' does not exist. However, the App Store Connect web UI uses the private endpoint below with the same payload and receives HTTP 201: POST https://appstoreconnect.apple.com/iris/v1/betaBackgroundAssetReviewSubmissions The public endpoint is also absent from the current App Store Connect OpenAPI specification. betaAppReviewSubmissions I also tested the public POST /v1/betaAppReviewSubmissions endpoint. When I supplied a backgroundAssetVersion relationship, the API returned 409: 'backgroundAssetVersion' is not a relationship on the resource 'betaAppReviewSubmissions'. You must provide a value for the relationship 'build'. The build relationship only accepts the builds resource type, not backgroundAssetVersions. Therefore, betaAppReviewSubmissions can submit an app build but cannot submit a Background Asset version. Could Apple please clarify: Which public API should be used to submit a Background Asset version for external TestFlight review? Is betaBackgroundAssetReviewSubmissions intended to be exposed through the public App Store Connect API? Is the link to betaAppReviewSubmissions in the Background Assets documentation incorrect? When will the public documentation and OpenAPI specification be updated? Thank you.

Hello, Our Digital Services Act trader verification has been showing "In Review" in App Store Connect since August 8, 2026. App name: Matchup Sport Apple ID: 6782085896 Account type: Individual, based in Austria Business > Agreements > Compliance > Digital Services Act: In Review, last updated August 8, 2026 (27 countries or regions) The trader declaration is set at both levels: the account-level declaration was submitted on August 8, and the app-level setting under App Information > App Store Regulations & Permits shows that the developer has identified itself as a trader for this app. Our planned launch territories are 13 countries, 12 of which are in the EU, including our home market of Austria. While this verification remains pending, the app cannot be distributed in any of them even once App Review completes. My questions: Is any document or information still outstanding from our side to complete the verification? Is there an expected timeframe for trader verification at present? Is there an escalation path if the status does not change? I have not been able to reach anyone on this specific topic through the standard support form. Any guidance would be appreciated. Thank you.

Hi, I'm trying to upload my app to TestFlight which contains the new iOS 27 CrashReporterExtension, however I'm getting this error: Invalid Info.plist value. The value of the EXExtensionPointIdentifier key, com.apple.crash-reporter.extension, in the Info.plist of “App.app/Extensions/CrashReporter.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. I'm guessing App Store Connect has not been updated to accept the crash reporter extension yet? Any idea when uploading an app with this extension will be possible?

Hi, I’m experiencing a recurring App Review issue with my app Lux Broker – Tycoon Game. This is not an isolated delayed submission. Almost every recent version of this app has followed the same pattern: Version 1.2.0: waited approximately 7 days before entering review, then review completed in about 5 minutes Version 1.3.0: waited approximately 7 days, then review completed in about 5 minutes Version 1.4.0: waited approximately 7.5 days, then was reviewed/rejected in about 4 minutes Version 1.4.0 resubmission: waited more than 8 days, then was approved in about 5 minutes I am now facing a more urgent situation with version 1.4.1. The currently released version contains a critical production issue that prevents affected users from opening the game. Version 1.4.1 was submitted on August 9, 2026 at 8:57 PM specifically to fix this issue. Because existing users are actively affected, I submitted an Expedited Review Request, and Apple confirmed: “We’ll expedite review for Lux Broker – Tycoon Game.” However, the submission is still in Waiting for Review and has not entered review. I have also contacted Developer Support regarding the issue. Apple ID: 6771816081 Submission ID: 2bb4927f-9a5f-4513-b390-5eec0a0fd216 Support Case: 20000132990094 My concern is not simply that one submission is taking longer than usual. There appears to be a consistent pattern affecting this specific app: submissions remain in “Waiting for Review” for approximately 7–8 days, while the actual review itself consistently takes only a few minutes. This has now become a critical production issue because the currently available version is preventing affected players from accessing the game. The fix is already submitted and the expedited review request has already been approved. Could someone from Apple please check whether this submission is correctly routed to the expedited review queue, or whether there is an app-level review routing issue affecting this application? Any help escalating this to the appropriate App Review team would be greatly appreciated. Thank you.

App ID 6794306744. Version 1.2.0 submitted 2 August, still "Waiting for Review" — six business days at the time of writing. I'm not posting to ask anyone to speed it up. I have a specific question about how expedited review requests are supposed to behave. I submitted two expedited review requests for this version. I have received: no confirmation that either request was received no notification that either was declined and I can find no representation of the request anywhere — not in App Store Connect, and not in the App Store Connect API So from my side a submitted expedite request is indistinguishable from one that was declined, and from one that never arrived at all. Is this the intended behaviour? On previous versions of this app expedite requests were granted within minutes, so I know the mechanism works — I just can't tell what happened this time. Two related questions for anyone who knows: Is there any surface (UI or API) where the status of an expedited review request can be seen? I've looked at reviewSubmissions and appStoreVersions and there's nothing there. Does an account lose access to expedited review silently after repeated requests? If so, is that communicated anywhere? For context on the submission itself: 7 items (the version plus two auto-renewable subscriptions and three non-consumables), all showing "Ready for Review", no errors, no missing metadata, build in VALID processing state. This is the first version of this app to include in-app purchases. Two support requests (5 and 8 August) have not been answered yet. If anyone else is currently seeing unusually long Waiting for Review times on a first submission containing IAPs, I'd be interested to know — it would help tell a systemic queue issue apart from something specific to my account.

I uploaded a build to testflight and released it to Internal testers, however when the testers tried downloading the app a alert dialog shows the following: Could not install [App] The requested app is not available or doesn't exist. Also tried to submit it via external testers but getting another error.

Hello Apple Developer Community & Support Staff, I am writing this out of sheer desperation. Our app has been stuck in the overall review process for nearly TWO MONTHS. Regarding our latest submission: Submission ID: aec29b9a-fbdf-41f3-b617-d593c2e29f70 Date Submitted: August 3, 2026 We completely understand that as a dating app, our submission requires strict adherence to UGC guidelines, robust user reporting/blocking mechanisms, and thorough content filtering. We have meticulously implemented all of these safety features and addressed every single issue previously raised by the review team. Recently, the status of this August 3rd submission finally changed to "In Review," which gave us hope. However, it inexplicably rolled back to "Waiting for Review" shortly after, with ZERO communication, messages, or explanations provided in the Resolution Center. We are hemorrhaging funds daily on server costs, delayed marketing campaigns, and operational expenses due to this silent, indefinite hold. If our app was escalated to a specialized team, or if there is a system glitch, we at least deserve to be informed. Could an Apple representative here please look into this specific Submission ID? We urgently need someone to manually check why this rollback happened and help us move forward. We are 100% ready to cooperate. Thank you.

I’d like to suggest an improvement to the App Review process, particularly around Guideline 2.1 – Information Needed for new app submissions. Recently, I submitted a new app and received a request asking for a screen recording demonstrating the app’s core functionality, along with information about tested devices, target audience, external services, regional differences, and other details. The problem is that I had already uploaded a screen recording when submitting the app. This makes the process frustrating and inefficient for both developers and Apple. If the information has already been provided, reviewers should ideally check the submitted materials before requesting them again. Otherwise, developers have to spend additional time responding, and Apple reviewers also spend additional time handling unnecessary back-and-forth. If a screen recording and these additional details are now effectively required for most new app submissions, I think Apple should make this part of the App Store Connect submission workflow. For example, App Store Connect could provide dedicated fields for: App demonstration video Tested devices and OS versions App purpose and target audience Test/login instructions External services and AI services used Regional differences Regulatory or licensing information, where applicable This would be much clearer than putting everything into a general “App Review Notes” field. In the AI era, the number of apps being created and submitted is likely to increase significantly. Apple’s App Review process needs to evolve alongside this. Repeatedly requesting information that developers have already supplied wastes time on both sides and creates unnecessary hurdles for developers trying to bring new ideas and innovations to the iOS ecosystem. I hope Apple can consider making these requirements more structured, transparent, and automated within App Store Connect. The goal should be to make App Review both more thorough and more efficient — for Apple reviewers as well as developers.

Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen