Publishing Apps from China (2026): Google Play Developer Verification and Apple Developer Phone Setup

The number on your developer account needs to last for years. Google Play and Apple both re-verify on key actions, and if the number lapses you're locked out.

Last updated: 2026-11-04
View giffgaff SIMsarrow_forward
On this page
  1. 1. How Strict Google Play and Apple Are Now
  2. 2. Tested: How Each Number Type Fares
  3. 3. Managing Several Entities: Keep Each One Separate
  4. 4. Why Get Your Developer Account SIM from LarkSIM
  5. 5. Fixing Common Verification Problems
  6. 6. Bottom Line
  7. 7. Frequently Asked Questions
  8. 8. Related guides

There are two common ways this goes wrong.

One: you sign up with a number from an SMS-receiving site, and months later Apple asks you to verify on a new device, so the code goes to a stranger. Two: several products share one phone number, one runs into trouble, and the others get pulled into extra review.

A developer account isn't a one-off signup. It's an asset you'll use for years, so pick a number you can control long-term from the start.

For an overseas number you can keep receiving codes on, LarkSIM's giffgaff physical SIM and US T-Mobile physical SIM ship from stock in mainland China as factory-new official cards, and the US plan renews with WeChat Pay or Alipay.

Platform rules are as of November 2026. Google Play Console and Apple Developer have the final word.

How Strict Google Play and Apple Are Now

If you still publish the way you did a few years ago, you'll probably hit a wall. The changes are in three areas:

  • check_circleGoogle Play personal accounts need a closed test: personal developer accounts created after November 2023 must run a closed test before production, currently at least 12 testers for 14 consecutive days. Signup also verifies your identity, address and phone.
  • check_circleOrganisation accounts must match D-U-N-S data: organisations need a D-U-N-S number, and the company name, address and phone you enter must match Dun & Bradstreet's records or verification stalls.
  • check_circleApple requires two-factor authentication: developer accounts must use 2FA, and the trusted phone number has to stay usable for signing agreements and logging in on new devices.

Tested: How Each Number Type Fares

Number TypeGoogle Play VerificationApple Developer BindingIsolation & Security Assessment
Mainland +86 number⚠️ Usually passes⚠️ Usually passesWorks, but every account hangs off one number, so trouble on one account can drag the others into review.
Google Voice / SMS-receiving sites❌ Often blocked❌ Often rejectedNot recommended: VoIP is easy to detect, and you don't control SMS-site numbers for future codes.
UK giffgaff physical SIM⭐⭐⭐⭐⭐ Smooth⭐⭐⭐⭐⭐ SmoothA UK mobile number on O2's network. Cheap, and good as a dedicated number for a UK entity or general account.
US T-Mobile physical SIM⭐⭐⭐⭐⭐ Smooth⭐⭐⭐⭐⭐ SmoothBest match for US entities and US accounts, and receives codes in China over Wi-Fi Calling.
Hong Kong SIM (HaHaSIM / Club Sim)⭐⭐⭐⭐⭐ Smooth⭐⭐⭐⭐⭐ SmoothFirst choice for HK entities and Asia-focused teams, with the cheapest keep-alive.
Based on developer signup and verification flows as of November 2026. Rules change, so check the official pages.

Managing Several Entities: Keep Each One Separate

If you have several companies, each publishing its own apps, the safest setup is to keep every entity's details completely separate:

  1. 1

    One phone number per entity

    Don't share a number across developer accounts for different entities. Give each one its own physical SIM, for example giffgaff for the UK company and the US T-Mobile SIM for the US company.
  2. 2

    Fixed devices and network per entity

    Log in to each entity's accounts from its own devices on a stable network, and don't keep switching between entities on one computer.
  3. 3

    Matching payment and payout details

    The card that pays Google's $25 fee or Apple's $99 annual fee, and the bank account that receives payouts, should belong to that entity. Don't mix them.

Why Get Your Developer Account SIM from LarkSIM

A developer account lasts for years, so its number can't be borrowed or likely to lapse. Our UK and US physical SIMs:

  • check_circleShipped from stock in mainland China, dispatched within 24 hours of payment. No waiting weeks for international mail.
  • check_circleFactory-new official cards: never activated, never resold.
  • check_circleNo foreign bank card needed to renew: our support team tops up the US plan and you pay in RMB with WeChat Pay or Alipay. giffgaff credit can be added with official £10 top-up vouchers.

Pick the one that matches your entity:

  • check_circlegiffgaff physical SIM: for UK entities or general developer accounts. A UK number for ¥99. One paid action every 6 months keeps it from being closed for inactivity. giffgaff has disconnected some numbers used long-term abroad, though, so keep only a small balance on it.
  • check_circleUS T-Mobile physical SIM: for US entities and US developer accounts: a real US +1 number, ¥199 including the first month. Wi-Fi Calling works on China-model iPhones, so you can receive codes over Wi-Fi in mainland China (the first activation needs an overseas network connection). Numbers are assigned at random, may have been used before and can't be swapped, and cards can't be returned once shipped.

Prices as of November 2026; see the product pages for current prices.

Fixing Common Verification Problems

  • check_circleGoogle says "can't verify this phone number": first confirm the number isn't VoIP, then check whether your network keeps switching or your IP looks unusual. Go back to a stable connection and retry with the physical SIM.
  • check_circleApple 2FA texts are slow: on a Hong Kong SIM or giffgaff, make sure the phone has roamed onto China Mobile or China Unicom. On the US SIM, wait until the status bar shows T-Mobile Wi-Fi before tapping resend.
  • check_circleYou get a verification call from the platform: overseas SIMs can take roaming calls in mainland China (roaming charges apply). Have your developer details ready and confirm them in English.

Bottom Line

Put your developer account on a physical SIM you can control for years, and give each entity its own number.

For a dedicated number for a UK or US entity, LarkSIM's giffgaff physical SIM and US T-Mobile physical SIM ship from stock in mainland China as factory-new official cards, and the US plan renews with WeChat Pay or Alipay.

Frequently Asked Questions

Does receiving Google Play and Apple codes in China cost anything?expand_more
giffgaff and Hong Kong SIMs receive SMS free while roaming on the mainland. The US T-Mobile SIM receives texts over Wi-Fi Calling as part of its monthly fee, with no extra charge.
My developer account was banned. Can I sign up again with a new number?expand_more
No, and don't try. Google Play policy forbids terminated developers from creating new accounts, and related accounts made with a new number or device are usually terminated too. Use the official appeal process instead.
Can several giffgaff SIMs share one phone for codes?expand_more
Yes. Swap them in when you sign up or verify, or use a dual-SIM phone, and codes arrive fine. Accounts for different entities should still be managed separately as described above.
Can a personal developer use an overseas SIM for Google's closed test?expand_more
Yes. Verifying with an overseas physical SIM doesn't affect the closed test. Follow Google Play Console's current tester count and duration.

Real UK +44 number · Ships from China · Chinese setup guides

giffgaff UK physical SIM

Register and manage a real UK mobile number yourself, shipped from local stock in China. The self-service SIM suits people who already have a way to top up; the worry-free SIM includes an official £10 top-up voucher.