Gyara "app not available" ga testers na closed testing na Google Play
An sabunta Nuwamba 2026
Testers ɗinka suna buɗe link ɗin sai Google Play ya ce manhajar ba ta nan, ba a same ta ba, ko ba ta dace da wayarsu ba. Kowace rana da wannan ke ci gaba rana ce da ƙirgar kwana 14 ɗinka ba ta aiki. Kusan koyaushe dalilin yana cikin ƴan matsalolin saiti kaɗan, kuma za ka iya duba su duka cikin kusan minti goma. Bi wannan jerin bisa tsari.
Jerin dubawa cikin sauri
- Shin release ɗin da ke closed track yana Published, ba In review ko Draft ba?
- Shin email ɗin tester (ko Google Group ɗinka) yana kan wannan closed track ɗin?
- Shin tester ya buɗe link na opt-in ya taɓa don zama tester?
- Shin tester ya shiga Google Play da wannan Google Account ɗin?
- Shin an zaɓi ƙasar tester don manhajar?
- Shin wayar tester ta cika mafi ƙarancin sigar Android da buƙatun na'ura da ka saka?
- Shin an shafe 'yan sa'o'i tun da aka fara wallafawa?
- Shin tester kuma yana cikin internal test ɗinka?
1. Ba a wallafa track ɗin ba tukuna
Google ya ce link na opt-in yana bayyana ne kawai idan matsayin manhajar Published ne. Idan closed release ɗinka na farko har yanzu yana cikin duba, ko an adana shi amma ba a taɓa aika shi don duba ba, testers ba za su ga komai mai amfani ba.
Buɗe Publishing overview. Idan akwai canje-canje da ke jiran a aika, aika su. Idan managed publishing yana kunne, canje-canjen da aka amince da su suna jira har sai ka danna Publish. Duba shafukan Inbox da Policy status ma don ganin ko an ƙi wani abu.
2. An wallafa shi 'yan mintuna da suka wuce
Google ya lura cewa bayan wallafawa ta farko link na gwaji na iya ɗaukar sa'o'i da dama kafin ya fara aiki, kuma canje-canje na gaba ma na iya ɗaukar sa'o'i da dama. Idan sauran komai daidai ne, jira rabin yini kafin ka canza wani abu. Canza saituna akai-akai na iya jawo sababbin dubawa su ƙara jinkiri.
3. Tester ba ya kan track ɗin
Gayyata ba ɗaya take da kasancewa a kan track ba. Buɗe Test and release, sannan Testing, sannan Closed testing, sannan Manage track, sannan Testers. Tabbatar an saka alamar jerin email da ke ɗauke da adireshin tester don wannan track ɗin kuma an adana, ko kuma an shigar da adireshin Google Group ɗinka a ƙarƙashin Google Groups.
Da Google Group, tester dole ya zama memba na group ɗin kafin ya yi opt in. Google ya ce membobin groups da aka ƙayyade ne kawai za su iya shiga gwajin. Idan kana amfani da Tester Exchange, group ɗin da za ka ƙara shi ne testerexchange-testers@googlegroups.com, kuma mu ne muke ƙara testers ɗinmu a ciki.
4. Asusun Google da bai dace ba a wayar
Wannan shi ne dalili mafi yawa ga abokai da iyali. Tester ya ba ka email ɗin aikinsa, ko kuma wayar tana da Google Accounts biyu kuma Play Store yana amfani da ɗayan.
Ka roƙi tester ya buɗe Play Store, ya taɓa hoton profile ɗinsa ya duba wane asusu ne yake aiki. Dole a buɗe link na opt-in yayin da aka shiga da asusun da ke jerinka, a cikin browser profile ɗaya. Sai ya sauke daga Play Store a wayar da wannan asusun. Idan ya zama dole, ƙara ɗayan adireshinsa a jerinka ma.
5. Tester bai taɓa yin opt in ba
Kowane tester dole ya buɗe link na opt-in ya karɓa, ɗaya bayan ɗaya. Aika musu link na Play Store kaɗai bai isa ba. Bayan sun karɓa, Google yana nuna link don sauke manhajar daga Google Play. Testers ba za su iya samun closed test ta hanyar bincike a Play Store ba.
6. Ƙasa ko na'ura ba a tallafa ba
Idan ƙasar tester ba ta cikin jerin Countries / regions ɗinka, manhajar ba za ta samu gare shi ba. Ƙara ƙasar; Google ya ce canje-canjen ƙasa suna shafar dukkan tracks.
"Your device isn't compatible" yawanci yana nufin mafi ƙarancin SDK ɗinka, fasalolin da ake buƙata (misali kyamara ko takamaiman tsarin CPU) ko keɓance na'urori sun fitar da wannan wayar. Duba Device catalog a Play Console. Wasannin da aka gina don 64-bit ARM kaɗai, ko masu manyan sigogin Android mafi ƙaranci, sukan fuskanci wannan.
7. Suna cikin internal test ɗinka
Google ya ce masu amfani da suka yi opt in zuwa internal testing ba su cancanci open da closed testing ba. Idan tester ya shiga internal test ɗinka a baya, dole ya fita daga ciki da farko (ya buɗe link na opt-in na internal ya bar shirin), sannan ya yi opt in zuwa closed test.
8. Play Store yana nuna tsohon yanayi
Idan duk abubuwan da ke sama daidai ne, ka roƙi tester ya rufe Play Store, ya share cache ɗinsa a Saitunan Android, ya sake gwadawa. Buɗe link na opt-in a Chrome na wayar maimakon cikin browser da ke cikin wata manhaja ma yana taimakawa.
Kare kwanakinka 14 yayin da kake gyarawa
Sharaɗin yana ƙirga testers 12 da suka ci gaba da opt in ba tare da tsayawa ba na kwana 14, don haka testers da ba su iya shiga ba ba sa taimakawa. Nemi wasu ƙarin testers (15 shi ne kyakkyawan manufa) don tester ɗaya da ya makale kada ya jinkirta gwajin gaba ɗaya. Tester Exchange yana maye gurbin testers da suka daina, kuma allon saitinsa yana gaya maka ainihin matakin Play Console da za ka ɗauka idan testers ɗinmu ba su iya sauke manhajarka ba.
Tambayoyin da ake yawan yi
Me yasa Play Store ke cewa "item not found"?
Yawanci ba a wallafa release ɗin ba tukuna, tester ya shiga da wani Google Account daban, ko kuma ba ya cikin jerin email ko Google Group na track ɗin.
Bayan wallafawa, bayan wane lokaci testers za su iya sauke manhajar?
Google ya ce link na gwaji na farko na iya ɗaukar sa'o'i da dama kafin ya fara aiki.
Shin testers da ba su iya sauke manhajar ana ƙirga su cikin 12?
Testers da suka yi opt in ne kaɗai ake ƙirgawa. Wanda bai taɓa iya yin opt in ba ba ya taimaka wa kwanakinka 14.
Shin testers za su iya samun manhajata ta bincike a Google Play?
A'a. Closed tests ba sa bayyana a bincike. Raba link na opt-in ko link na Play Store.
Shin sai na sake wallafawa bayan na ƙara testers?
Ƙara email a jeri ko membobi a Google Group ba sa buƙatar sabon release. Adana canje-canjen shafin Testers ka aika su idan Publishing overview ya nemi hakan.