Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Forget the <code>self.delegate</code> error for now, it is a red herring if <code>[self class]</code> is producing the wrong result! Your results suggest you are somehow clobbering <code>self</code>.</p> <p>Breakpoint on <code>webView:didFinishLoadForFrame:</code> check the <code>self</code> value and step through.</p> <p><strong>Comment Followup</strong></p> <p>For self to be wrong on the first statement of an instance method is, let's say, unusual (but not impossible).</p> <p>It is important when an object is set as another's delegate that you make sure the delegate object's lifetime is at least as long as the one it is acting as a delegate to. Introducing ARC can make previously working code fail as it may release the delegate earlier than the code did under MRC. When this happens the call to the delegate usually fails.</p> <p>However your error does not fail on the call to the delegate; the call starts - you end up in <code>webView:didFinishLoadForFrame:</code> - and then you find <code>self</code> is invalid. To actually invoke an instance method <em>usually</em> requires a valid value for <code>self</code> as it is used to determine the method implementation to call. Hence it is usual for <code>self</code> to be valid at the start of a method!</p> <p>But note the "usually"...</p> <p>So despite you having successfully reach your method, your error might be down to not having a strong reference to your <code>SubFoo</code> instance, you pass it as a delegate to <code>aWebView</code>, and by the time <code>webView:didFinishLoadForFrame:</code> is called your <code>SubFoo</code> has gone.</p> <p>Make sure you're keeping a strong ref to your <code>SubFoo instance</code>. If you just want to test (this is <strong>not</strong> a recommended general solution!) if this is your problem you can just assign it to a local static (<code>static SubFoo *holdMe</code> say declared inside <code>performRequest</code>) in <code>performRequest</code>, which will keep a strong reference around at least until the next call to <code>performRequest</code>. If this does prove to be the problem you then need to come up with a good way to maintain the reference that fits your design.</p>
    singulars
    1. This table or related slice is empty.
    1. POWeird memory issues, with ARC enabled
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCRD
    1. USCRD
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWasn't sure how to check the self value using gdb, so I just did NSLog(@"%@ %p", self, self); right after webView:didFinishLoadForFrame:. First, it crashed with an EXC_BAD_ACCESS. I tried to run it again, and this time it outputted ( "<WebHTMLView: 0x10232ac90>" ) 0x102301060. Which means that self is really getting clobbered, somehow...
      singulars
      1. PO
      1. USEduAlm
    2. COThe NSLog statement that you are currently using works fine. You can even omit the call of NSStringFromClass as the class method retuns an object of type Class which is perfectly capable of describing iself. In your xcode while debugging split the debugger window into two. (see the icons in the top right of the debugging console part of the window and chose the one in the middle). Then in the left hand pane within the debug window you will see self, its class and poperties and its superclass and properties and so on. If that does not work then repeat your NSLog after each statement.
      singulars
      1. PO
      1. USHermann Klecker
    3. CODid that. Sometimes self gets set to random things right on the webView:didFinishLoadForFrame:.
      singulars
      1. PO
      1. USEduAlm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload