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
Devcon 2020 Goes Virtual! LEARN MORE >

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

PhoneGap app stops working after I publish changes

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    PhoneGap app stops working after I publish changes

    So my phonegap app is a single component with many panels and lists that obviously occasionally needs updating (whether its fixing errors that never occurred before, adding new tools, or just making minor updates). But an issue I am running into is if I make changes to the component and then save it and publish it and create a new phonegap version so I can can do testing with test filght I run into an issue where the app that is already out in production stops syncing with the server. Are these two things correlated and if so what do I need to do to prevent this? I think my only option (unless there is some setting I am missing somewhere) would be to create a duplicate of my base component and essentially test my updates as a "second app" and then make that new component the base component in the phonegap builder once I've made sure all the changes are working properly, is that my only option?
    Tags: None
    #2
    Re: PhoneGap app stops working after I publish changes

    If you publish a new component, the old one is gone form the server yet the old one is trying to make calls. My experience is that if you update an app - those who installed it must also.
    Maybe you can turn on hyrdration in PGB to alert users to install the updated version. Now, through my own testing I have had cases where hydration would somehow get caught in a loop causing teh update to fail - but to be honest I do not have a lot of experience behind me so perhaps someone can chime in with a good solution for you.
    I would suggest creating a new app for testing and once complete, send out a notification to update. I am assuming you have no other option to notify users automatically of course.
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment

      #3
      Re: PhoneGap app stops working after I publish changes

      Yeah I pretty much assumed that first part (when I publish the changes the "old" component doesn't exist anymore), just figured there might be something already baked into the alpha anywhere server/software to handle this since there isn't a host of warning messages pertaining to this (and being there will always be an inherent delay since the App Store has a review process).

      Looks like the only option is to duplicate the current production component and make changes to this new test component (publishing, saving and uploading to phonegap and testing) and then once everything is ready to go delete the current production component, rename the test to the same name as the current production, republish the component and then save and upload to phonegap. However, as mentioned above there is still a small issue here since after getting the ipa file for the App Store and uploading it to iTunes Connect there is still the app review delay (which means until that is done the current app in production won't work). So really this solution only shortens the amount of downtime for the app in production rather than completely fixing the issue.

      Greatly appreciate your feedback Charles and look forward to other gurus chiming in with some other helpful info. I'll also be thinking about going back to a web app that is made to look native and just deal with the fact that it has to be reloaded every time it is opened on an iOS device (at least in this case every change is made live right when I publish).

      Comment

        #4
        Re: PhoneGap app stops working after I publish changes

        Yeah, iOS is a painful process no doubt. So far my web app built for iPads seems to be the best way as I don't need apples approval to run a web component adn update it as I see fit and users don't have to do a thing...except login.
        I kind of actually like telling people that there is nothign to download or install - just login - from anywhere and from any web enabled device!
        I am of course building an iOS app and an android but I keep coming back to the many benefits of the web browser!
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment

          #5
          Re: PhoneGap app stops working after I publish changes

          Yeah I agree there’s a lot of power in having a Web app and I may just have to go back to that as well!

          Comment

          Previous template Next
          Working...
          X