Debugging in AppCode

Open the file specified in the error message and go to line 27. To do this, you can press ⌃⇧N and in the dialog that opens type <filename>:27.

Thanks to the do...catch block used in this code fragment, we can see that the error occurred on decoding the JSON file.

Set a line breakpoint at line 24: click the gutter area left to the code line or press ⌃F8.

Start the debugging session by pressing ⇧F9. The program execution stops at the line where the breakpoint is set, and now we can examine the current program state in the Debug tool window that opens:

The Frames tab displays a stack of method/function calls, and the Variables tab — a list of variables available in the current context. At this point, we see that the conference data (the conferenceData variable) is successfully loaded from the local JSON file. The error that we’ve got (Expected to decode Double but found a string/data instead) most likely relates to the JSONDecoder object which hasn’t been created yet.

Click or press F8 to execute the next code line — let decoder = JSONDecoder(). Now look at the Variables tab: the decoder variable has appeared and you can see all the properties of the newly created JSONDecoder object when expanding this variable. If the value is truncated, click View to open it in a popup:

Now we know that our JSONDecoder uses the deferredToDate decoding strategy that can handle dates in double format only, whereas we have the string date values in our JSON.

Let’s try to change this behavior using the formatted decoding strategy instead. To do this, set a breakpoint right before the decode() method is called, namely, at the following line:

Press ⌃⇧F8 to open the Breakpoints dialog:

Delete the breakpoint at line 24 since we don’t need it any longer: you can either click it in the editor or delete it from the Breakpoints dialog by clicking or pressing ⌦.

In the Breakpoints dialog, select a breakpoint at line 25 and check the Evaluate and log option. In this field, you can type the code that you want to execute when the breakpoint is hit. Click to expand the text field and type the following code:

For the symbols visible in the current context, auto-completion is available:

Press Done and rerun the program in debug mode by pressing ⌃F5 or clicking the button on the Debug tool window.

Now when the application is suspended, you see the decoder.dateDecodingStrategy property has a new value which cannot be displayed correctly on the Variables tab:

You can use the LLDB console to see such values. Go to the LLDB tab and type the following command:

Now our decoder uses the formatted date decoding strategy:

Press F8 to step over to the next code line and go back to the Variables tab. The conferencesData variable now stores the values from the parsed JSON file:

Resume the program by pressing F9 and make sure that the list of conferences is now displayed on your device or simulator:

Since the code injected on the breakpoint hit has fixed the bug, you can add it in the editor:

Delete the breakpoint at line 25 by clicking its icon.

Go to the file and line specified in the error message (press ⌃⇧N and type <filename>:<line number> ), set a line breakpoint ⌃F8 at the first line of the textDates() method, and press ⇧F9.

On the device or simulator screen, select the dot Swift conference to reproduce the bug. On the Variables tab and in the editor, you can see that the end date of the chosen conference equals nil:

So, we see that the application is going to crash after executing line 17, more precisely, when trying to unwrap an optional value:

Let’s try to set a non-nil value for the end variable to ensure that it is the reason for the bug. Select the end variable on the Variables tab and press F2. In the text field that appears, type Date(), press ⏎, and press F8 or click to execute line 17.

The application doesn’t crash now because we’ve set the current day as a value of the end property:

To fix this bug, replace the code of the textDates() method with the following:

Run the application and check that now the dot Swift conference description opens without errors.

Set a new breakpoint at line 21 (⌃F8) and remove the previous one at line 17 by clicking its icon in the gutter.

We want the new breakpoint to stop the program execution only when the end and start dates of the conference are the same. For this purpose, we can create a special condition: right-click the breakpoint and in the Condition field type end == start:

Run the application in debug mode ⇧F9 and select random conferences from the list. The program execution will stop only when the specified condition is satisfied, for example, on selecting the Mobilization conference:

Now when the program is paused, and the Debugger tab is available, let’s add the result variable to watches, which will allow us to observe the variable state in a separate tab. To do this, right-click the variable on the Variables tab and select Add to Watches. If the Watches tab is currently hidden, click the button and select Watches in the list.

You can add any variable you want to observe to watches. For example, you can also add the name variable to see the name of the current conference.

To fix the bug, write a condition that handles the equal start and end values. Firstly, change the result value at runtime using the Evaluate and log field of the Breakpoints dialog ⌃⇧F8:

Resume the program execution F9 and choose other conferences from the list. When a conference has the same end and start dates (for example, Mobilization or Mobile Optimized 2019 ), the execution will stop. On the Watches tab, you will see the correct value of the result variable:

Since the code added at runtime has fixed the issue, you can add it in the editor and rerun ⇧F10 the application:

Go to the Breakpoints dialog ⌃⇧F8, click , and select Symbolic Breakpoint. In the Symbol Name field, type the following:

Press ⇧F9 to start debugging and open the same link. The program execution will stop at the method specified for the symbolic breakpoint, and you will see the disassembled code of this method in the dedicated view:

Go to the LLDB tab of the Debug tool window and type the following command in the LLDB console:

This will return the first parameter of the method the debugger stopped at:

This is an invalid URL passed as a parameter of the open(_:options:completionHandler:) method.

Go to iOSConferences/Resources/conferencesData.json and correct the misprint: