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



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

Problems with PhoneGap Android camera creating database records

  • Filter
  • Time
  • Show
Clear All
new posts

    Problems with PhoneGap Android camera creating database records

    Trying to create a very simple app, to store a picture and some basic information about the picture, using the excellent video and samples provided. Using latest AA 2.0 version, MySQL on ZebraHost. App is supposed to allow user to fill a few text boxes with information, take a photo and upload this to the database on web site (next phase will involve a login to the site, ability to examine records and create custom reports.) App itself will get a little more complicated, but I'm try to start with simple stuff, get it working and then enhance :)

    So far, the app will upload records into the database from both Live Preview and Working Preview from with my AA Developer Edition (except for the camera photos, understood) but FAIL without explanation when I try to do the same using the same app on my actual SG4 phone - no records wind up on the database. An additional problem is that for those records that do make it to the database, they are "doubled" - that is, there are two identical (except for auto-incremented primary key column) records created. I have tried numerous and various options on the PhoneGap part of the app.

    I know this may not be enough information to obtain much help, but perhaps I am missing something easy and obvious (to everyone else); I'd be happy to provide more detailed information if asked.

    Re: Problems with PhoneGap Android camera creating database records

    Hey Simon,

    If you want to send me your UX I can have a look and see if there's anything out of the ordinary that would keep it from working live.

    Send me your PhoneGap Projects folder as well so I can see how the PhoneGap Build properties are set.

    Send me a private email via this forum (click on my forum name) with your email address and we can go from there.

    You're not set up for private email otherwise I would have responded that way.




      Re: Problems with PhoneGap Android camera creating database records

      Thanks, David, I'll get right on that - was gone tonight until just now. Much appreciate any help you can provide!


        Re: Problems with PhoneGap Android camera creating database records

        Hey Simon,

        Got your files and I've got the app working.

        There are some basic processes that I think we all miss when first working with this stuff... and even after working with it a lot... still miss... well... I do anyway. Really basic stuff.

        First... in your Server-side afterDialogEvent... you have 2 ExecuteServerSideAction statements. 2 actions means 2 records.

        As an aside this could be very cool. Run the first action... change the record a bit via code in between the two actions... run the 2nd action. I'll have to remember that.
        Anyway... in this case... this is not what you want so delete one of the actions.

        Second... and this is probably why things are working under LivePreview but not on your device... did you publish the UX? The Component needs to be published to the default location... usually A5Webroot.

        When you test under LivePreview the component is automatically published to A5Webroot/LivePreview. So that's why it works.

        I'll guess that if you simply hit the publish button things will work. You'll be publishing to Local Webroot... which is usually [C]:/A5Webroot.

        Under the menu item Web, Project Settings, for Local Webroot, you'll see a Target Property. Here you can put a folder name so that publshing to Local Webroot will publish to [C]:/A5Webroot/yourtarget.

        If you do this, then you need to change the PhoneGap Build property URL for all Ajax Callbacks. For example I have mine set to because my Web Project Settings Target folder is Inspection. So... when I publish... my UX goes into the Inspection folder under Webroot.

        Delete your app from your device, re-publish to PhoneGap Build from Alpha, re-install your app, and all should be good.


          Re: Problems with PhoneGap Android camera creating database records

          Stupid me; I replied 15 days ago with big 'Thank you!' but did so from my email, totally over-looking the all-cap warning not to do that very same thing :(

          What I said: "Thank you very much, David - I'll follow your directions and see how much better this will be :) I really appreciate your taking the time to help; you're clearly one of the Good Guys. "

          Then, a couple of days later, I said: "So, it took a bit more work for me, because it turned out I had misunderstood the connection (actually, the lack of same) between the database on Zebrahost and my "local" one, but your help with Publishing made all the difference. That plus I had goofed up on the IP address on ZH - I actually have two IP/instances set up on ZH and used the OTHER one. But I found that error quickly, once I 'published' correctly."

          Anyway, thanks for the help, David :)