Please don't install APKs you receive through WhatsApp. That is actually how you end up with malware on your phone. As far as the conclusion you reached, I believe that if you would be publishing...
Please don't install APKs you receive through WhatsApp. That is actually how you end up with malware on your phone.
As far as the conclusion you reached, I believe that if you would be publishing your app to the play store you'd be blocked from uploading it to begin with. See this support article.
Use a proper way to distribute test builds? Although sure, for testing within a team I'd say you can make an exception. I more meant it as a more general remark, don't install APKs from unknown...
Use a proper way to distribute test builds? Although sure, for testing within a team I'd say you can make an exception.
I more meant it as a more general remark, don't install APKs from unknown sources. In most cases outside your specific one you cannot properly trace the origin of the APK.
I don't know how mobile development tests their builds. But I imagine if it's not in a VM/emulator/etc., then it's a mobile device provided specifically for testing. As opposed to a personal device.
I don't know how mobile development tests their builds. But I imagine if it's not in a VM/emulator/etc., then it's a mobile device provided specifically for testing. As opposed to a personal device.
You create a new version on Google Play or Apple AppStore, and create an internal / alpha test group. You add your team to that group. Android testers need a link to the Google Play store page...
You create a new version on Google Play or Apple AppStore, and create an internal / alpha test group. You add your team to that group. Android testers need a link to the Google Play store page only they can see, and Apple testers see it all in TestFlight. If all is fine, you can actually publish the version, or just step up the test to a second-level group.
Both platforms' testing first happens in an emulator, but Apple's is much worse, so sooner or later you need to link a phone to your IDE, and it will build straight to it. I see no real reason to avoid using a personal device honestly.
Also in my experience 99% of all install errors are caused by signing issues.
They might be located in a country where a large portion of Android phones come without the play store. So that might make that process a bit of an impossibility. Still, if it is available using...
They might be located in a country where a large portion of Android phones come without the play store. So that might make that process a bit of an impossibility. Still, if it is available using the proper tooling and platforms does make sense.
For sure, even for dogfooding there are better methods of distributing the build as Minty already pointed out. I was merely saying that as far as receiving APKs through WhatsApp this at least is...
For sure, even for dogfooding there are better methods of distributing the build as Minty already pointed out. I was merely saying that as far as receiving APKs through WhatsApp this at least is the one with less of a risk factor.
@pyeri, since you're relatively new to Tildes, and this is the second time in a row you've posted one of your own user created articles, I think it's worth pointing out Tildes self-promotion...
@pyeri, since you're relatively new to Tildes, and this is the second time in a row you've posted one of your own user created articles, I think it's worth pointing out Tildes self-promotion rules. I'm not trying to totally discourage you from posting your work here on Tildes, but I wanted to point out the rules just in case you weren't aware of them, and so you don't inadvertently get banned for spamming:
Self-promotion
If you have your own site/project/channel/etc. that you'd like to share on Tildes, that's generally fine (in moderation), but it shouldn't be the primary reason that you post on the site. Tildes is a community, not a free advertising platform. Sharing your own content is welcome as long as you're involved in the community, but don't just treat Tildes as a source of an audience.
I could be wrong, but I'm pretty sure pyeri only just recently returned to the site after being temp banned. So while I normally wouldn't feel it was worth making such a warning comment to anyone...
I could be wrong, but I'm pretty sure pyeri only just recently returned to the site after being temp banned. So while I normally wouldn't feel it was worth making such a warning comment to anyone else merely posting 2 user created posts in a row, so long as they also had a bunch of other interaction on the site... I thought it was worth warning OP about the self-promotion rules so that they don't inadvertently end up getting banned again (perhaps permanently next time) for potentially breaking another rule immediately after returning to the site after an extended absence. So a bit of column A, a bit of column B in this particular case.
Please don't install APKs you receive through WhatsApp. That is actually how you end up with malware on your phone.
As far as the conclusion you reached, I believe that if you would be publishing your app to the play store you'd be blocked from uploading it to begin with. See this support article.
In that case, how will you send it to your testing team if you want to get it tested before publishing on the Play Store?
Use a proper way to distribute test builds? Although sure, for testing within a team I'd say you can make an exception.
I more meant it as a more general remark, don't install APKs from unknown sources. In most cases outside your specific one you cannot properly trace the origin of the APK.
I don't know how mobile development tests their builds. But I imagine if it's not in a VM/emulator/etc., then it's a mobile device provided specifically for testing. As opposed to a personal device.
You create a new version on Google Play or Apple AppStore, and create an internal / alpha test group. You add your team to that group. Android testers need a link to the Google Play store page only they can see, and Apple testers see it all in TestFlight. If all is fine, you can actually publish the version, or just step up the test to a second-level group.
Both platforms' testing first happens in an emulator, but Apple's is much worse, so sooner or later you need to link a phone to your IDE, and it will build straight to it. I see no real reason to avoid using a personal device honestly.
Also in my experience 99% of all install errors are caused by signing issues.
They might be located in a country where a large portion of Android phones come without the play store. So that might make that process a bit of an impossibility. Still, if it is available using the proper tooling and platforms does make sense.
For sure, even for dogfooding there are better methods of distributing the build as Minty already pointed out. I was merely saying that as far as receiving APKs through WhatsApp this at least is the one with less of a risk factor.
@pyeri, since you're relatively new to Tildes, and this is the second time in a row you've posted one of your own user created articles, I think it's worth pointing out Tildes self-promotion rules. I'm not trying to totally discourage you from posting your work here on Tildes, but I wanted to point out the rules just in case you weren't aware of them, and so you don't inadvertently get banned for spamming:
https://docs.tildes.net/policies/code-of-conduct#self-promotion
p.s. Please label this comment as Offtopic so it doesn't detract from any on-topic discussion.
I could be wrong, but I'm pretty sure pyeri only just recently returned to the site after being temp banned. So while I normally wouldn't feel it was worth making such a warning comment to anyone else merely posting 2 user created posts in a row, so long as they also had a bunch of other interaction on the site... I thought it was worth warning OP about the self-promotion rules so that they don't inadvertently end up getting banned again (perhaps permanently next time) for potentially breaking another rule immediately after returning to the site after an extended absence. So a bit of column A, a bit of column B in this particular case.
Thanks for pointing out the concern @cfabbro, I will keep this in mind.
YVW. And thanks for taking the warning/advice in the spirit in which it was intended. Welcome back, BTW. :)