A spreadsheet of emails is not evidence that every person can install your app. The important outcome is that the intended accounts have access to the correct track and can complete the joining flow.

Prepare a clean working copy

Keep the original list privately and edit a separate copy. Remove accidental spaces, blank rows and exact duplicates. Do not invent spelling corrections: ask the owner when an address looks wrong. Count unique addresses before and after importing so a missing account is easier to spot.

Play Console supports tester email lists as well as Google Groups. Choose the method your team can maintain; a group is not required when using an email list.

Verify the saved configuration

After importing, reopen the list and compare the saved count. Then check that this list is actually selected on the intended closed track. A correctly created list that is not selected will not solve access.

Before replacing an existing import, check the current Console behavior and keep a backup. Do not assume a new file simply appends to an old list.

Test with a real recipient

Ask one authorized person to open the opt-in link using their listed account, join and attempt installation. Record the result and only then distribute the same instructions to everyone.

Keep email addresses out of screenshots used for public marketing. For internal tracking, use a private sheet with account, invitation date, confirmed access and unresolved issue. Do not label someone as participating merely because their address exists in a file.