What Should I Do if My App Has a Bug or Crashes?
No one wants errors in their software development project, but knowing what to look for and how to react may help mitigate many problems. It will also make the problem easier to relay to the developer so the problem can be rectified as soon as possible. We will define what a bug and a crash is, and then we will go through the initial steps, or troubleshooting, that a product owner can consider doing to try to solve the problem. Once we go through the preliminary methods of solving the problem, we will describe the details that the app founder might provide the app developer or IT specialist to get the problem resolved as quickly as possible with the least amount of back and forth and time wasted.
Questions that are addressed in this article include the following:
- What is the difference between a bug and a crash?
- What are some things to try if I have a problem with my app?
- What types of info about the error can I provide that will help my app developer or IT specialist fix the problem?
- What is the best method of relaying information to the developer or IT specialist?
What is the difference between a bug and a crash?
A bug occurs when a feature of an app does not work as it was designed or in the way that’s unexpected. They are sometimes caused by the creativeness of the user coming up with functions or uses of the app that were not intended. There are many types of app errors that will be discussed in a future blog, but a few common types of bugs include the following:
- Not being able to properly sign in to the app.
- A field of a form not saving properly.
- A shopping cart not updating as new items are added.
- Push notifications not going through as intended.
- The design or layout of the app is not looking as intended.
These are only a few of the many bugs that can exist. Bugs can vary widely depending on the purpose and functionality of the app. Another thing to keep in mind is that, in some cases, an app could be working as it was designed, but there was a misunderstanding between the developer and the product owner on how certain aspects of the app should function, so the product owner initially considers it to be a bug. If the product founder and the app developer communicate and collaborate regularly and the product owner points out things that appear to be amiss with the app from the beginning, those types of issues might be discovered early and worked on promptly.
What people often refer to as a software or app crash is also a type of bug: what you expected to happen doesn’t happen. What people think of as a “crash” causes an app to go down completely or does not allow the user to proceed further. Such would be the case if the app “freezes”. This type of bug can possibly be discovered when the product owner or end user visits an app and it doesn’t open at all or will not allow them to log in. A crash can also sometimes be caused when a user fills out a certain field or taps a certain button on the app and it stops working, not allowing the user to move forward in the app.
What are some things to try if I have a problem with my app?
When a product owner realizes that there appears to be a problem with an app, there are certain things that can be tried before getting the software developer or IT specialist involved. A bug or crash can be caused by a fault in the software itself, but it can also be caused by external factors not directly related to the app. It may be a good idea to try to eliminate other possible causes of the app’s malfunctioning, to do a little “troubleshooting”, before notifying the developer about the issue. The app founder can try the following ideas:
- Refresh the app.
- If unable to refresh the app or if that doesn’t appear to work, totally close and restart the app.
- Restart the device you are using the app on, whether it be a computer, phone or some other device. Sometimes a bug does exist, but it’s in the device and not in the app.
- Restart the internet. This may work if a crash is actually a connectivity issue.
- If in a situation where you cannot restart the internet, try using the app again when your source of connectivity changes.
- When the app appears to not be working at all, make sure your bills are paid to your internet service provider and to the developer. This sounds silly, but “errors” caused for this reason sometimes occur.
- Check to see if other websites or apps are acting properly on your device to totally eliminate that it’s a connectivity issue.
- If your app has a security certificate, make sure that it is up to date and hasn’t expired.
- If it’s a web app, make sure that the URL you are using is correct. One small error in the address is enough to make the entire app unresponsive. Also, inputting “http” instead of “https” in the URL can often make a difference. This is especially true if you are filling out a form, using any form of GPS location finding tool or maps, are posting pictures or documents through the app, or doing anything that requires the app to have extra security. Some things will not work properly with just “http”.
If an app founder tries to troubleshoot the error by trying these different ideas and the problem still exists, it may be time to report the issue to the app developer or IT specialist.
What types of info about the error can I provide that will help my app developer or IT specialist fix the problem?
When an app owner has ruled out other possible causes of an app’s bugs, it may be time to get the app developer or IT specialist involved to identify and fix the problem. If that’s the case, the developer or specialist may want specific info to help them diagnose the issue and come up with a solution. To avoid what may seem like an endless amount of back-and-forth the app founder can gather much of the info the developer or specialist may need prior to writing that email or making that call:
- Provide details on exactly what’s occurring with the bug. Note what you expected to happen and what actually occurred.
- Give the date and time in which the error occurred including the time zone.
- If possible, take a screenshot of the issue including any error message received. If the issue occurred on a website-based app, include the web address (URL) in the screenshot.
- Inform the developer or IT specialist of the device you were using, its operating system, and the type of browser you were using (if applicable) when the problem occurred.
- Give the pathway you took to get to the error. The pathway is every step you took, buttons you pressed, and forms you filled out prior to the error occurring.
- If a user and not the founder is the one having the problem, the app founder should attempt to duplicate the error on their own device and report this information to the app developer or IT specialist. If the error appears to be happening with just one user or a group of users, acquire the above information regarding their systems, internet, and devices so the problem can be localized.
By supplying this type of information, the developer or IT specialist should gain what they need to be able to find the problem that is occurring with the app and determine the best way to correct it.
What is the best method to relay information to the developer or IT specialist?
All of the required information that the developer or specialist needs is sometimes difficult for an app founder to describe and relate. Sometimes, the error occurs so quickly that the founder doesn’t even notice all of the steps or realize exactly what is occuring. When the app error is occurring on a mobile device such as a cell phone, a good way to provide much of the information in a straightforward way that developers would benefit from is for the app founder to record their cell phone’s screen, showing the entire process they went through for the error to occur. By doing so, the developer can see exactly what happened, which will increase their chances of being able to duplicate it. Once a developer or IT specialist can duplicate the error, they may have all of the information they need to determine what is occurring and derive a solution for the issue.
To find out other problems that can occur when developing an app, besides errors, visit the Matraex Insights blog, “What Are Problems that Occur When Developing an App?”. You can also contact us, give us a call at (208) 344-1115, or place a question on our Google Business Page. Matraex is a premier desktop and mobile app development company based in Boise, Idaho. Our goal is to help consumers with their app development and technology questions so they can be informed consumers. We’d love to help with any questions that you may have about apps or app development so you are always informed and can make the right decisions for you or your company concerning app development. We look forward to hearing from you.
Sign up to receive answers to your questions delivered directly to your inbox!
XenCenter – missing ‘Logs’ tab
XenCenter – missing ‘Logs’ tab
Xencenter has moved the status of actions somewhere for each Physical and VM from the very intuitive ‘logs’ tab location it was before. Here is where they moved it.
- At the bottom of the left pane there is an option called ‘Notifications’, when you click it you are automatically shown all of the the alerts (such as the status changes)
- At the top of the left pane whn you are clicked on Notifications you will notice that it has given you three options “Alerts”, “Updates” and “Events”.
- If you click on “Events” you will see the status of ongoing ‘Exports’ or transfers or other actions.