Home/ Questions/Q 8336743
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T04:05:24+00:00

I’ve developing my first iOS app which allows users to login to an account

  • 0

I’ve developing my first iOS app which allows users to login to an account on our website, and view / add / edit / delete records in a database.

I’ve written a basic app which handles the process like this;

App starts running.

Each view controller calls a checkAuth method from within the viewWillAppear method. This method gets the username and password stored within the app, sends them to the server as GET variables in a dataWithContentsOfURL request. The resulting JSON is then checked, if the response is a failure, then an alert dialog is shown, and the user is taken to a different tab (I’m using a tab bar controller) where they are prompted to enter their login details.

Using this method, every time a different view controller takes over (each scene in my storyboard file), the auth method is called. This seems a little wasteful. Is there a better way of ensuring a users login credentials are correct?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Storing the username and password in the app is bad practice. If modifying the back end is within your control, it would be better to authenticate to the back end, and get back a token that is only good for that device.

    From here, you pass the token along with each request, and if the back end determines you have logged out then it should return an error message. This way, the authentication would be checked on an ad-hoc basis and only when sending a request.

    I see no reason to do it every time a view loads, unless there is a business requirement for this.

    • 0