I noticed that every device registered in our database for our
just-approved app is showing up as having declined all push
notifications. None of our testers' devices had this problem, and I
couldn't repro it on mine. Of course, testing this is nearly
impossible, because Apple gives developers
Our app won't build right now because of this:
ld: file is universal (1 slices) but does not contain a(n) armv7s
slice: /projects/libcrypto-device.a for architecture armv7s
But lipo says:
Architectures in the fat file: /projects/libcrypto-device.a are: armv7
I've cleaned the project
armv7s
note the s on the end.
Thanks. What is armv7s, and how does one compile for it? A quick
search didn't reveal any obvious references to it online. I'm using a
build script for OpenSSL that configures the build for armv7.
___
Cocoa-dev
Thanks. Yes, I was well on the way to sorting it out, but I was just
waiting for the build to finish to report back.
I was able to easily add armv7s to the build script, and it seems to
be progressing happily.
There's a bunch of info here:
Are obviously rogues, using crazy technologies like toolbars and maps.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at
We have an app in the store that's now broken because a critical
screen's toolbar is blank. There's nothing funky done to present it;
the screen is just a view loaded from a XIB, which has the toolbar and
buttons defined. Worked fine up until iOS 6.
Anybody else see a problem like this?
We have a problem where some underlying data changes, so we go through
the annotation collection for a mapview and change the affected
annotation (in this case its title); and when the associated marker on
the map is tapped, the displayed text isn't changed.
In other cases, an annotation is
Never mind. The problem was an incomplete array of annotations I was maintaing.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at
Thanks for that suggestion. I'm only reloading visible cells, so I would
expect them to already be instantiated and readily available in memory.
However, if cellForRow... is called, I guess there is an attempt to
dequeue. I'd have to take a look at how much time is spent in that method.
At any
Asynchronous programming means you'll be called back when things happen,
and in the meantime you should return control so other stuff can run. It
doesn't mean that you should go into an infinite loop trying to force
something async to run synchronously.
That question was rhetorical. The
I found that this only happened when 51 pixels or fewer of the last row of
a section were visible at the top of the screen. The row height returned
was 97. So 51 was a baffling number, not being half the row height or of
any other significance I could see.
Turns out that the tableview specified
Actually, I spoke too soon. This problem continues to occur, but the
critical position of the partial row at the top varies with the table's row
height. And it's not even always the bottom portion; sometimes if the last
row in the previous section is cut off in a middle region, rendering will
On Mon, Jul 23, 2012 at 8:16 AM, Fritz Anderson fri...@manoverboard.orgwrote:
I think the first problem you should concentrate on should be the
multiply-overlaid drawings. It's hard to tell what's going on unless you
share some code, or at least your design, so I can only ask general
Though probably off topic, this is unnecessary work. If you just want to
change where your arrow is pointing, you should reach into the cells and
change the position of the arrow - you shouldn't be doing a reload for
that. Think something more like for (UITableViewCell* cell in [tableView
I just saw this somewhere today and now can't find it. There's a place (in
the Apple Provisioning Portal somewhere maybe) where you can specify a
string that will be presented to the user (in place of the default one)
when the app asks for permission to use push notifications.
Anybody know where
Since my app has nothing to do while waiting for the sound to play
I struggled with this when getting into iOS programming and networking;
everything's asynchronous, and you can't just have your UI locked up. So
what is my app to do while it's waiting? It's a fundamental programming
problem
I have a tableview that contains some graphic elements that rotate to
reflect the phone's heading. I only reload the visible rows, and I don't
do it while the table is scrolling. I filter the headings to 10-degree
increments to cut down the amount of heading updates I get.
Sometimes these work
I found the exact condition that results in this problem. The corruption
only happens when
1. There's more than one section on the screen.
2. The last row of the topmost section is only partially visible, and the
visible portion is smaller than the section header.
The part about the section
But I am stumped as to how I might be able to more or less seamlessly
handle syncing the file between the Mac and the iOS device.
This is perhaps the most glaring and insufferable omission in the SDK. I
urge you to file a bug report on this and tell Apple that you want to be
able to sync
I added some new operation-handling in my app, and it's now crashing quite
frequently in background threads with EXC_BAD_ACCESS and this:
1 Foundation0x306cdd46
-[NSObject(NSKeyValueObservingPrivate)
_changeValueForKey:key:key:usingBlock:] + 438
2 Foundation
Never mind. I was double-releasing an operation.
Thanks anyway!
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
I have a screen that can be flipped over to show a map, and from the map
the user can invoke a detail controller for an item on the map. So I
instantiate a navigation controller, make the map controller its root-view
controller, and then invoke it:
- (void)showMap
{
StashMapController*
Ugh, never mind. The graphic files hadn't been added to the project. I
would've expected a warning message to the console or a blank button, but
got neither.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
I have a UIImageView in a custom TableViewCell that I want to rotate to
arbitrary angles. When I apply a rotation transformation like so:
CGAffineTransform rotation = CGAffineTransformMakeRotation(15 * (M_PI /
180));
[self.thumbImageView setTransform:rotation];
The image is not only rotated
Thanks for the reply, Julius. I had the mode set to
UIViewContentModeScaleToFill.
Setting it to UIViewContentModeCenter does allow the image to rotate
undistorted, but the frame is still ridiculously distorted. And look at
the massive difference in distortion for a tiny difference in angle
On Tue, Jun 26, 2012 at 7:38 PM, Joe Wollard joe.woll...@gmail.com wrote:
Out of curiosity, why are you manually removing them in the first place?
MKMapView should be handling that logic for you as I understand it. If its
for performance, the docs say to make sure you dequeue the
After the user drags the map, I do a query and update the pins on it. To
prevent flashing of all the pins, I add the new (complete) collection of
annotations before removing the old ones. I call addAnnotations before
removeAnnotations.
But the pins still flash. The map goes completely blank
Am I overlooking it in the doc, or does the doc fail to state that the
segmented control acts like a radio button? This appears to be wrong:
A UISegmentedControl object is a horizontal control made of multiple
segments, each segment functioning as a discrete button. A segmented
control affords a
Thanks, guys.
I knew that this is how it usually works, but started wondering because the
doc seems to go out of its way NOT to mention it. How can you write
multiple (wrong) descriptions of this control without noting this
fundamental aspect of its function?
Not to mention the poor design of
Hi all.
When our app gets a notification that it's going into the background, it clears
the tableview that serves as its primary UI element. However, when the app
returns to the foreground, it still briefly contains the items that were
supposedly cleared. They remain there for a second after
30 matches
Mail list logo
