I use the latest opentok Android SDK to development an application. My purpose is to provide a button to let user can publish / unpublish camera. It works to unpublish the camera using publisher.setPublishVideo(false); , but it doesn't work to republish when I use publisher.setPublishVideo(true);.
And I also try to use publisher.destroy() to delete the publish and recreate the publisher and then publish it, however since publisher.destroy has been called, either publisher and subscriber's video all disappear. It's very weird.
Am I using the wrong way or could anyone give me a hint?
OpenTok's Android SDK is still in beta so its has errors here and there. You have caught an error, and this error has been reported to OpenTok. Will update when this error has been resolved.
edit- This bug will be fixed in Android 1.0.1
Related
Working on the new feature In-App-Update released in Google I/O 2019. Implementation is done as per the documentation.
Link : https://developer.android.com/guide/app-bundle/in-app-updates
App looks for the new updated, if update found app downloads the new version and then install it.
Problem here : After installing app restarts. Again app shows update is available. Same flow appears. Stuck in this loop.
Can anybody has the experience in this in app update?.
I found resolution:
In-app update works only if You installed a signed apk
Also do not forget to add to onResume handling method for DEVELOPER_TRIGGERED_UPDATE_IN_PROGRESS.
Everything already written in Official Manual.
I am trying to upload an app bundle to the Google Play Store, and the play console shows an error message:
"An error occurred with running the bundle-tool for your uploaded app
bundle. Ensure that your app bundle is valid and try again. Learn
more. Error:"
I run the bundle-tool on my own computer and everything works just fine.
Anyone knows why this happens?
https://developer.android.com/studio/projects/dynamic-delivery#create_dynamic_feature
you may need this. although the doc is not detailed.
You need to deploy aab files only, .apk is not allowed anymore. It was made compulsory from august. It was notified already
Did you run "build-apks" with the latest version of bundletool?
If so, there is little we can do to help here without access to the actual bundle. I would recommend reaching out to Play Console support team: they will be able to investigate.
For anyone else who happens to stumble upon this issue, make sure you download and use the latest version of bundle-tool, my issue was duplication of FILE-PATH-PROVIDERS, the old bundle-tool let it slide, latest one does not
Im trying to rollout a new beta release of an android app.
I have uploaded the apk file to the Google Play console.
But in the release page I get the following warning:
While it says it is just a warning, I am unable to proceed with the rollout.
And as there are no other errors or warnings, I'm assuming the reason I cannot continue is due to this warning.
This app is only installed on 2 devices - the developers devices. The warning has no real consequences, as the app is in beta.
Is there anyone way to get passed this warning?
Same things happened to me with the version code 2. so I built and uploaded new apk with version code 3. Don't know how but it did work!
The rollout could be blocked because other parts of the app info you need to fill in are not complete.
On the left panel, make sure all the check marks are green.
This shouldn't block your rollout. If it is blocking your rollout, or something else is and the Play console isn't telling you what it is, then it is a bug in the Play Console. Please contact the Play Console support (using the Contact section under the help "?" icon) and they can check your exact details and work out what is going wrong. They can provide support using email and live chat.
It happened to me when migrated to androidx.
The numbers of affected devices for the new version was insignificant. (1 device out of 7000+)
I decided to continue with the rollout in spite of this warning.
Just upgraded an app from V12 to V13 - text change in help only. Works fine.
Go up upload it to dev. console and it will not publish the new APK, says:
"This configuration cannot be published for the following reason(s):
Version 12 is not served to any device configuration: all devices that might receive version 12 would receive version 13."
What is it talking about? V12 was published for 40K+ devices, I've just done exactly the same thing to three other apps with no problem, but this one won't have it.
No idea what it means. All I can do is save it as draft.
I think it is known problem of Google developer console.
Please see this answer
When you upload a new version of an app, you need to manually deactivate the previous version, until you do, the dev console won't let you publish the new state.
Both answers above equally good. I had tried the second one and it didn't work. Went back a few hours later, still didn't work, did the second answer again, and it did. Very strange ....
You have 1.1 version app already developed and is released in market & you are about to send update(release new version 1.2 ) in Play store/itunes with some critical functional changes.
What are the ways do you follow to simulate situation like real time App Update that happen in Play store/itunes? How do you test that?
Common things which i cross checked before :
Android
Ios
Sample Scenario :
I'm trying to trace down a database upgrade bug and need to figure out a
way of simulating market upgrades.
You can actually release into Play store as alpha and/or beta and test upgrade this way. It's best as it's a real upgrade from the store, nothing simulated.
You can read more here: https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
EDIT
You can also try something like that: have a copy of the code of the previous version. Upload it to a test device. Then upload the new code, this will force a database update which you will be able to debug.