I'm trying to develop a watch app for the Gear S3 Frontier. I had been mistakenly testing with the Tizen emulator on Tizen 3.0, but have discovered that my push notification implementation does not work in 2.3.2 (which is what is on the S3 now). I have checked and rechecked against every example I could find, but cannot seem to receive push notifications. It works fine with 3.0, but the altered version that uses the 2.3.2 method of connecting simply never receives any notifications. The Samsung push API reports success when my server sends, but I never get anything on the watch or emulator in 2.3.2. I saw that this post asks a similar questions but was never fully answered and I don't have the rep to comment on it. Does someone have a working example of this?
I solved it. I discovered an error in the logs that indicated that it was looking for the "appData" field. The documentation says that you can include EITHER "appData" or "message", but it appears that you must have BOTH present in 2.3.2. Tizen 3.0 doesn't seem to care.
Related
I developed an app that'll stream a rtmp video. Before I used VitamioBundle-master. I upload my app in play store it shows some warning message for upgrading my app that has to use vitamio latest version. I download it from the link shown in that alert message. Now I develop the app using vitamio 5.0.2 downloaded from the link https://www.vitamio.org/en/Download/. Once I upload the app play store shows the same alert message
Security alert
Your app utilizes a version of Vitamio, a multimedia library used for playing various types of media files, containing a security vulnerability.
Please upgrade your app(s) as soon as possible and increment the version number of the upgraded APK. Beginning 14 March 2016, Google Play will block publishing of any new apps or updates that use pre-5.0 versions of Vitamio.
The vulnerability was addressed in Vitamio v5.0. The latest versions of Vitamio can be downloaded on the Vitamio website. You can confirm your Vitamio version by checking if the SDK includes libs/armeabi-v7a/libvinit.so or libs/armeabi/libvinit.so. If either file is present, the SDK needs to be upgraded. For help upgrading, see the Vitamio support documentation. If you’re using a 3rd party library that bundles Vitamio, please notify the 3rd party and work with them to address this.
To confirm you’ve upgraded correctly, submit the updated version to the Developer Console and check back after five hours. If the app hasn’t been correctly upgraded, we will display a warning.
The vulnerability is due to the Vitamio SDK containing world-writable code. For more information about the vulnerability, please see this NowSecure blog post. For other technical questions, you can post to Stack Overflow and use the tags “android-security” and “vitamio.”
While these specific issues may not affect every app that uses Vitamio, it’s best to stay up to date on all security patches. Apps with vulnerabilities that expose users to risk of compromise may be considered in violation of our Malicious Behavior policy and section 4.4 of the Developer Distribution Agreement.
Apps must also comply with the Developer Distribution Agreement and Developer Program Policies. If you feel we have sent this warning in error, contact our policy support team through the Google Play Developer Help Center.
I gone through several solutions mentioned in different tutorial but not yet get a clear idea. Can anyone tell me the step by step procedure for updating my vitamio sdk version, or else is there any other lib for streaming rtmp video in my Android app?
Unfortunately, Vitamio 5.0.2 added back the old libvinit.so file, so it gets flagged as an old version of Vitamio. You can just delete libvinit.so and it should work.
Years ago, I created a SWF application that enabled users to perform online video chat. It used simple SMTFP publish/play method to stream video. Now a few years passed and i am trying to create a backward compatible SWF application.
My problem status:
New version fails to play the streams that are published from the old swf. It
connects to server and to the publisher, but it cannot play and gives
the NetStream.Play.Failed error.
New version plays the streams that are published from its own version.
Online players like in this
guide can play my new version, but they are unable to play
streams from my old version.
I tried it with different SDKs (3.6, 4.1, 4.6) and they all fail to play the old swf streams.
I searched the web for the error and documents don't clear anything and they are just saying that it is a general error. There is question in SO that could be related, but it has no answers.
Does anyone know the reason? or any suggestions?
Are you sure that the same publication names are used in both applications? It is possible that you publish a stream with name "test1" for example and the player try to play the stream with name "test2".
Otherwise if you think that the names are correct you can try with MonaServer, it is our own open source server. It supports RTMFP, RTMP[E], HTTP and Websocket (also RTSP for testing only). Install it on your computer/server and check the log to see what's going on.
I found the problem. It seems like the flash player has changed RTMFP protocol in 11.1 version. There is not much documentation about it and as far as i can understand, I should either upgrade all the flash players or I should upgrade all of the old applications to flex 4 sdk.
I am working on an iOS app which need to get push notifications(using GCM) from web service(Made of Python).
Currently the web service works fine with Android devices, but it reports Error=MismatchSenderId, when I check this error in the online doc, it suggests the sender_id and API_key are not matched. The thing is, as I understand it(could be wrong), for iOS SDK, unlike the Android's, it doesn't need sender_id.
The tricky part is I have no access to the web service yet(which the collaboration party claim the Android app works fine with it). Could anyone shred a light on what steps should I take to fix this issue?
THanks in advance.
My Android app uses BLE APIs, and one of these APIs, BluetoothGattCallback.onConnectionStateChange(), receives an undocumented error code 19. I'm using Nexus 9.
Did anybody ever see this error code before? Like I mentioned above, this is undocumented in the Android API reference, and I don't know what to do about it.
P.S.
I searched issue tickets at Android issue tracker also, and found that developers encounter undocumented, BLE-related error codes often. Hmm, this is grim.
I need support in SignalR for Android client. I am using following client SignalR/Java-Client but unable to know where to start :) We are completed .net self host & working fine. But only problem with Android & iPhone. Can any one please guide me how to start the next steps for Android & iPhone.
You don't give a lot of details, so it's hard to give a concrete answer, especially since your question is very broad to begin with. Nonetheless, you should have a look at the official samples for the Java client, to get you started. If you have implemented the server side yourselves, and know your Java, it should be pretty easy to figure out from the code provided in these samples. The Java client is, in my experience, very easy to use.
As for an iOS client, a Google search came up with this library. I have never used it, and it looks like it's not getting a whole lot of support, but you could always give it a shot.