Phonegap 2019 geolocation

step 1
https://speeltuin.nl/thewayback/
update the code and compile with Phonegap Build – submit you IPA

step 2
get an annoying e-mail:

Dear Developer,

We identified one or more issues with a recent delivery for your app, “The Way Back”. Please correct the following issues, then upload again.

“Missing Purpose String in Info.plist File. Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSLocationAlwaysUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting spring 2019, all apps submitted to the App Store that access user data will be required to include a purpose string.If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).”

“Missing Purpose String in Info.plist File. Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSLocationWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting spring 2019, all apps submitted to the App Store that access user data will be required to include a purpose string.If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).”

Best regards,

The App Store Team

step 3a
try to find a solution, like
https://github.com/apache/cordova-plugin-geolocation/issues/142

step 3b
Check if *-Info.plist actually changed and keep on seaching and trying.

step 4
figure out the real solution:

   <config-file platform=”ios” parent=”NSLocationWhenInUseUsageDescription” target=”*-Info.plist” mode=”overwrite”>
        <string>Allow GPS to find the Way Back</string>
    </config-file>
    <config-file platform=”ios” parent=”NSLocationAlwaysUsageDescription” target=”*-Info.plist” mode=”overwrite”>
        <string>Allow GPS to find the Way Back</string>
   </config-file>

That’s all folks!
Just contact My Brain if you need help….

419 HTTP status code

… does not exist
https://nl.wikipedia.org/wiki/Lijst_van_HTTP-statuscodes

However it did take some of my time to figure this one out as the response code was really in my webserver logfiles and as usual… I was not the first to run into this problem, see: https://stackoverflow.com/questions/46266553/why-laravel-api-return-419-status-code-on-post-and-put-method

You get a 419 status code, if an (external) script tries to post to your Laravel application, without the o-so-needed CSRF token.

First option is to change in App\Http\Middleware\VerifyCsrfToken:
protected $except = [ ‘/*’, ];
(or maybe something more specific and a little more safe, like ‘/myapiurl/*’,)

Second option is to put the route in api.php instead of web.php, but that implies prefixing all your routes with /api/

… your choice!

The Joel Test

bron: click here.

The Joel Test: 12 Steps to Better Code

Have you ever heard of SEMA? It’s a fairly esoteric system for measuring how good a software team is. No, wait! Don’t follow that link! It will take you about six years just to understand that stuff. So I’ve come up with my own, highly irresponsible, sloppy test to rate the quality of a software team. The great part about it is that it takes about 3 minutes. With all the time you save, you can go to medical school.

The Joel Test

  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

Continue reading The Joel Test