Announcement

Collapse
No announcement yet.

Issues with vbulletin v 2.01 apps iOS and Android

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    https://tracker.vbulletin.com/vbmapp/issues/VBM-55
    SENT messages in iOS app do not append to the existing PM thread in which you are replying

    https://tracker.vbulletin.com/vbmapp/issues/VBM-56
    iOS app spellcheck autocorrect will not engage as typing a message to send

    https://tracker.vbulletin.com/vbmapp/issues/VBM-57
    Android app once emoji keyboard is engaged hard to revert to regular ABC keyboard

    https://tracker.vbulletin.com/vbmapp/issues/VBM-58
    Android app stuck in jsonArray error can't get it to open

    Comment


    • #17
      By the way, and this issue has been Confirmed and marked as Major, but for me, of all of the bugs this one really is the worst. I won't even use the iOS app to respond to PMs due to this issue, rendering the iOS app useless for me until this is fixed:

      https://tracker.vbulletin.com/vbmapp/issues/VBM-55
      SENT messages in iOS app do not append to the existing PM thread in which you are replying

      This seems to be a bug exclusive to the iOS app. 2.02

      I used the iOS app to Reply to a PM thread that had some messages in it. Later, when I accessed the PM thread on the website message, I noticed that the reply I had made was not there at the bottom of the thread.

      I thought that perhaps I had forgotten to push Send, but then when I examined SENT messages, the reply PM was there, but all by itself, not attached to the PM thread from which I had replied.

      Android app does not exhibit this issue. I created a test thread to PM back and forth between myself and another forum member. Replies made using the iOS app do not append - do not become a part of the existing PM thread, but replies from the Android app do append and become part of the thread normally.

      I created a thread with one PM sent from user M to user J, and one PM sent from user J to user M. Then I sent a PM using the iOS app from user M to user J:

      https://i.imgur.com/Lk6M7JK.jpg


      and I also sent a message from user M to user J using the android app:

      https://i.imgur.com/la4Bxve.jpg


      However then when examining the thread later in the website version, either looking from user's M's side or user J's side:

      https://i.imgur.com/KGN0oLM.jpg

      https://i.imgur.com/bWrv2uW.jpg

      only the reply sent using the Android app becomes a part of the existing thread.

      The reply sent with the iOS app, somehow becomes an independent PM, in some new thread that is created:

      https://i.imgur.com/vHWjNL3.jpg


      such that there are now two threads

      https://i.imgur.com/Szv1Xtu.jpg



      https://i.imgur.com/b4KaGnr.jpg

      This is not good! Replies using the iOS app should remain within the existing PM thread, not becoming a new PM for a newly created thread of its own.

      Comment


    • #18
      https://tracker.vbulletin.com/vbmapp/issues/VBM-53
      was closed and this new bug tracker was opened:
      The drop down list only matches people in your Friends list, not the whole forum. This is to prevent spam. The semi colon issue will be fixed in https://tracker.vbulletin.com/vbmapp/issues/VBM-59

      Comment


      • #19
        The Android app is in danger of being pulled, just received this, which I assume is related to at least these bugs, maybe others too:

        https://tracker.vbulletin.com/vbmapp/issues/VBM-40
        Facebook login not working for iOS or Android apps

        https://tracker.vbulletin.com/vbmapp/issues/VBM-45
        Android app, inexplicably gave this error AppError [code: client_connection_error, extra: null,exception: javax.net.ssl.SSLPeerUnverifiedException: Cannot verify hostname:

        https://tracker.vbulletin.com/vbmapp/issues/VBM-46
        Android app intermittent error: AppError [code: connection_error, extra: No internet connection, exception: null]

        https://tracker.vbulletin.com/vbmapp/issues/VBM-58
        Android app - error AppError [code: client_connection_error, extra: null, exception: java.lang UnsupportedOperationException: The method parseOutput(JSONArray jsonArray, IHTTPRequest httpRequest) is not implemented for com.vbulletin.server.requests.apimethods.ActivityServerRequest )

        Got this email from Facebook today:

        Hi,

        In working to create a great Platform experience for everyone, we ask developers to ensure the apps they build comply with our Platform Policies. Your app XXXXXXXXX Android iOS login (AppId: 6897XXXXXXXX1225) doesn't comply with the following:

        Platform Policy 1.2: Build an app that is stable and easily navigable. Be sure your app insights reflect a positive experience.

        Here's a visual example of the policy: https://developers.facebook.com/policy#1-1-photo.
        Some common violations of this policy include:
        - Broken Facebook integration (e.g. broken login or canvas integration)
        - Broken functionality in the app (e.g. share functionality is broken)

        Platform Policy 8.1: Verify that you have integrated Login correctly. Your app shouldn't crash or hang during the testing process.

        During Login, your Android app is crashing or hanging excessively, creating a broken experience for people trying to use your app. To make sure this flow runs smoothly, check that you've integrated Facebook Login correctly. We recommend that you test Login on all integrations. If you have not already done so, please:

        Here's our quickstart guide for implementing Facebook Login for Android: https://developers.facebook.com/docs...-login/android
        We encourage you to test your Login integration following these steps here: https://developers.facebook.com/docs...ur-login-flow/
        Best Practices for Login can be found here: https://developers.facebook.com/docs...best-practices


        You can access the full list of our Platform Policies here: https://developers.facebook.com/policy/.

        Please make the requested changes by 2019-08-11 at 12:00 PST.

        Let us know when you've updated your app by replying to this email. If we do not hear back from you, your app will be subject to enforcement. If you have outstanding questions, respond here and we'll do our best to help.

        Thanks,

        Regina

        Comment


        • #20
          Facebook Login has been hotfixed. Rebuilding the app in the Mobile Publisher should restore this functionality.

          The other issues will be worked on in 2.1 of the app as far as I am aware. This is currently under development.
          Translations provided by Google.

          Wayne Luke
          The Rabid Badger - a vBulletin Cloud customization and demonstration site.
          vBulletin 5 Documentation - Updated every Friday. Report issues here.
          vBulletin 5 API - Full / Mobile
          I am not currently available for vB Messenger Chats.

          Comment


          • #21
            Unless I am mistaken, I did upload that hotfixed version - is there some version of the Android app that was created after 7/12/2019, that is the last time I created and uploaded the Android app.

            Comment


            • #22
              *Update* Facebook deactivated that Facebook developer's app. However it turns out that this was a second app I had created for Facebook login to my forum iOS app and Android app, that I was not using. (I created another one, pretty much identical other than one additional Key Hash, and that Facebook app is still working (not deactivated)). I checked login functionality on website, iOS app and Facebook app and it worked for all three.

              So, whether Facebook deactivated this app because it was missing the Key Hash, or because it wasn't even connected to the forum apps (different Facebook App ID / different Facebook App Secret), I don't know, but for now things are still working Facebook login wise across the board.

              Comment

              widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
              Working...
              X