Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

data cache refresh fails in mobile app

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

    data cache refresh fails in mobile app

    I've got some data cache items that work fine online, even on browser on a tablet, but the same UX refreshing the same data cache items fails, and actually has an alert popup that says "failed" coming from something in AA code, not mine.

    There's a message in the console log that tells me the "onBeforeDownloadStart" function is being called, which makes me think the JSON file is being created on the server. But the Response from the server doesn't have the data. I'm running on IIS; is there something in Alpha or IIS that needs to be set to allow the session files to be accessed? I'm accessing session files from the browser already.

    Any suggestions are welcome.

    #2
    Hey Chris, you are using the exact same ux and it's only failing when used on a cell phone device? Computer or tablet is ok, cell phone isn't?

    Comment


      #3
      Thanks for the reply. I agree my original request wasn't clear. I actually figured out yesterday that it's working as expected against a different server environment.

      Same UX for browser and for the mobile app
      Same AA build on both servers
      Same database structure on both servers (but different data in databases)
      Similar IIS setup on both servers (though there are probably some settings that are different)
      The only obvious difference I see is that the failing server is running from a subdirectory (http://www.mysite.com/path/myA5WPage.a5w instead of http://www.mysite.com/myA5WPage.a5w)

      Server 1 from Browser works (on computer and mobile devices)
      Server 1 from Mobile App works
      Server 2 from Browser works (on computer and mobile devices)
      Server 2 from Mobile App fails

      Comment


        #4
        Just for testing, did you try to publish on the second server without using a sub folder and see if the problem goes away?

        Comment


          #5
          Okay I'm re-opening this as I'm having troubles again. We've been testing and developing, but had been able to put this issue on the back burner for a while. Here's what I know now. First of all, you have to make sure your samesite settings are correct. Alpha documents this.

          Server 1 Test Server on app - http - works
          Server 2 Pilot site on Production server on app - http - works
          Server 2 Pilot site on Production server on app - https self-signed cert - doesn't work
          Server 2 Pilot site on Production server on Chrome browser - https self-signed cert - works
          Server 3 Pilot site on Production server on app - https purchased cert - works

          The part that's not working is the Alpha built-in data cache download used with dropdown lists, etc. When in Chrome, the JSON data is created on the server, compressed and put into the browser's local storage. On the mobile app, the JSON data is created on the server, then stored in JSON as a file on the device. That's the only difference I know of other than the SSL, but the app works okay with SSL for Server 3 using https. I'm getting beat by this thing.

          Comment


            #6
            This is interesting. My guess is that the self signed certificate is getting automatically blocked behind the scenes within the webview of the app.

            Comment


              #7
              Hello. I know this is an old post, but I am seeing similar behavior in my app. It happened after I installed nightly build 8308 for testing on IIS Server. I always install new versions of Alpha in their own directory as to not interfere with production. After doing this, all IIS apps that use data cache were simply getting the alert "failed" when refreshing the data cache, even production apps using build 8000 of Alpha. I managed to get it working with one app by simply publishing again, or at least I think that is what got it working. However, I have another app where this just does not seem to be working.

              The error is HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

              Requested URL: /myappName/A5SessionFile/myDataCacheName.json

              Any insight that anyone could give me would be greatly appreciated.‚Äč

              Comment


                #8
                Please disregard. I think I figured it out. On the app where it was working, I had Cookie SameSite value set to Unset, which I remember Sarah saying recently needs to be Unset on all Cordova apps. The app that was not working had SameSite value set to strict. I changed to Unset and published again and it appears to be working. Attending the weekly Alpha Q and A paid off for me! Thanks Sarah!

                Comment

                Working...
                X