|
Doctor w-rw-rw- posted:"Because it crashes" isn't a really good reason to not deploy to iPads - I think that making the effort to fix your app for iPads is probably going to be the best use of your time. Meanwhile I can work towards a fix, but also I don't want people downloading it on iPad if it doesn't work on it for the time being. By the way, it crashes when it asks for access to Photos and the user selects OK, which should set it to "Read and Write". dc3k posted:I'm able to repro it every time. Tried on a bunch of different filters, both front and back camera, photo and video. Are you using 13.1? Someone else's iPad and iPhone crash when hitting Back on 13.1. My guess is it's not ready for that OS for some reason. e: crap iOS 13 is being released in two days lol Good Sphere fucked around with this message at 22:52 on Sep 17, 2019 |
#
?
Sep 17, 2019 20:09
|
|
|
|
| # ? May 16, 2024 00:11 |
|
|
Ugh I'm boned on crash reporting. I switched development machines and left my xcarchives behind for my deployed apps. So I've got crash reports coming in and no way to symbolicate them. I don't have bitcode turned on, so can't grab them from iTunes Connect either. *sigh*
|
|
#
?
Sep 18, 2019 05:58
|
|
|
lord funk posted:Ugh I'm boned on crash reporting. I switched development machines and left my xcarchives behind for my deployed apps. So I've got crash reports coming in and no way to symbolicate them. I don't have bitcode turned on, so can't grab them from iTunes Connect either. Let this be a lesson to practice proper backup hygiene - stuff you've shipped, put in a redundant place, even if it's just dropbox.
|
|
#
?
Sep 18, 2019 12:52
|
|
|
iOS 13 problem with Hue Cycle app: I have a modal view with a video playing (AVPlayer with AVPlayerLayer). I found that in iOS 13 it crashes when I dismiss this modal view, and Xcode's console says "AVPlayerLayer was deallocated while key value observers were still registered with it". I found that I was removing the playerLayer and making the playerLayer nil, or else more of the device's memory would be consumed each time you dismiss the view. Now that it crashes in iOS 13, I can comment out removing playerLayer and making playerLayer nil, but that brings me back to the memory problem; eventually terminating my app. code:edit: I had a key path observer I was never getting rid of! I added: pl.removeObserver(self, forKeyPath: "videoRect") which fixes the crash, but the memory footprint keeps growing, and eventually crashes. I wonder if it's the video, but maybe something else. Good Sphere fucked around with this message at 17:41 on Sep 18, 2019 |
|
#
?
Sep 18, 2019 17:20
|
|
|
Ah sorry I forgot to mention I’m on iOS 13 beta. Glad you found the issue!
|
|
#
?
Sep 18, 2019 19:00
|
|
|
Me too, though I hope I can still make my target OS lower than 13 without problems. I also still have a fairly bad memory leak.
Good Sphere fucked around with this message at 19:12 on Sep 18, 2019 |
|
#
?
Sep 18, 2019 19:09
|
|
|
Good Sphere posted:Is there a way of preventing your iPhone app showing up in the App Store for iPads? I know it will as an iPhone-size app when launched, but my app does not seem ready for it since it crashes. My app's settings under Deployment Info lists only iPhone for Devices. no, and your app may be rejected for not running on iPad
|
|
#
?
Sep 19, 2019 05:22
|
|
|
anecdata: The iPhone 4S was the first iPhone released with a dual core CPU, and was otherwise impossible to differentiate from the iPhone 4 for the purposes of shipping to the app store. While the app benefited a lot from the second core, Apple didn't allow us to differentiate on that basis, and didn't allow the BLE entitlement which would have allowed us to ship on 4S and above. Even if you found a workaround, you'd just spend time waiting for Apple to reject your app until you fix it.
|
|
#
?
Sep 19, 2019 05:39
|
|
|
Is it true that enabling Malloc Stack under Diagnostics >> Memory Management takes up space in documents and data for an iOS app? I was wondering how the space was piling up, but it seems to have stopped when I unchecked it, and reinstalled.
|
|
#
?
Sep 19, 2019 18:24
|
|
|
brap posted:The .reloadRevalidatingCacheData flag did exactly what I wanted, but there was a remarkable bit of documentation for the cache flags: You should file this as a docs bug. VVV https://feedbackassistant.apple.com Family Values fucked around with this message at 19:58 on Sep 19, 2019 |
|
#
?
Sep 19, 2019 18:26
|
|
|
Family Values posted:You should file this as a docs bug. Where’s the right place to do this?
|
|
#
?
Sep 19, 2019 19:38
|
|
|
Anyone know if there's a way to see who uploaded each build in ASC?
|
|
#
?
Sep 19, 2019 20:43
|
|
|
Nvm, found it (select app, Activity tab, "app store versions" in sidebar)
|
|
#
?
Sep 19, 2019 21:04
|
|
|
stuffed crust punk posted:Anyone know if there's a way to see who uploaded each build in ASC? Is it an App Store version? We don't have multiple roles, but I'm guessing in Activity >> App Store Versions the user column may tell you. e: nooo my one attempt to help someone, and I was already too late 
|
|
#
?
Sep 19, 2019 21:08
|
|
|
In fairness to fastlane, their support is fantastic. Well poo poo, there I was thinking it was a problem...... edit: Yoink. That image came out bigger than I expected o_O
|
|
#
?
Sep 20, 2019 05:03
|
|
|
That poo poo's infuriating. Just leave the issue open!
|
|
#
?
Sep 20, 2019 05:08
|
|
|
pokeyman posted:That poo poo's infuriating. Just leave the issue open! Its one way to point the burndown chart south I guess. Just close the ticket without resolving it!
|
|
#
?
Sep 20, 2019 06:42
|
|
|
PMs love to freak out about having a huge number of open issues without being able to explain why it’s a problem.
|
|
#
?
Sep 20, 2019 07:03
|
|
|
Nah, auto closing issues is a good practice. It helps with actual prioritization and understanding where the real problems are.
|
|
#
?
Sep 20, 2019 16:32
|
|
|
Good Sphere posted:Is it an App Store version? We don't have multiple roles, but I'm guessing in Activity >> App Store Versions the user column may tell you. Thanks anyway dude 
|
|
#
?
Sep 20, 2019 16:41
|
|
|
Doh004 posted:Nah, auto closing issues is a good practice. It helps with actual prioritization and understanding where the real problems are.  Triage and filter. Closing pisses people off.
|
|
#
?
Sep 20, 2019 18:41
|
|
|
Yeah, in GitHub you should just tag issues and put them in milestones. Closing the issue takes it from “we would accept a fix, but it’s unlikely the team will ever get around to it”, to “a bot decided your problem must not be a problem after all”
|
|
#
?
Sep 20, 2019 18:46
|
|
|
Those bots will attempt to see if it's still a problem being experienced by pinging people following the thread. If there's no more movement then it closes it (ie: https://github.com/fastlane/fastlane/issues/15134). I'd say a week turnaround is a bit too tight in my book but tickets timing out is definitely a thing.
|
|
#
?
Sep 20, 2019 19:13
|
|
|
CIFilters behave differently in iOS 13. So far, I found: CIMaskToAlpha - expects a monochrome image, or else some adjustments you made to the image prior to the filters could have unexpected results, like intensity of white crossing back into black. CIEdgeWork - completely messed up by putting edge work on every single tiny detail There could be a lot more.
|
|
#
?
Sep 20, 2019 19:33
|
|
|
Doh004 posted:Nah, auto closing issues is a good practice. It helps with actual prioritization and understanding where the real problems are. How does it help with actual prioritization and understanding where the real problems are?
|
|
#
?
Sep 20, 2019 21:49
|
|
|
Plorkyeran posted:How does it help with actual prioritization and understanding where the real problems are? If they're real problems that are relevant, it'll probably be occurring to more than one person (for larger projects that would employ something like this) so the issues wouldn't become stale.
|
|
#
?
Sep 20, 2019 22:28
|
|
|
Why would it not become stale? The initial report comes in, there's maybe a bit of discussion, and then it gets tossed into the backlog. Future people who have the same problem mostly find the issue, see that you're aware of it and then close the page. 6 months later you ping the original author and they don't respond because they already gave up on using your thing, and none of the other people who saw the issue and cared about it get pinged because who the hell hits follow on every single bug in a third party thing that they hope gets fixed (or they do hit follow and don't see your ping because they get 500 emails a day from github). Even in some fantasy land where a meaningful portion of the people who care about seeing a bug fixed actually tell you that, what are you gaining from closing old issues? You obviously already have a great way to figure out what issues are most important that's much more accurate than "ehhh there's been no activity on this for a while I guess it must not matter?"
|
|
#
?
Sep 21, 2019 00:14
|
|
|
It's also really discouraging to start using a thing and then find the exact issue you were having described months ago in a now-closed bug report. If you're using the thing for the first time's kinda discouraging. It might help if Github had some sort of "soft closed" state that makes the issue count go down but non-owner users are able to ask to reopen it. It seems like that would reduce friction for someone who comes along with a repro + it would keep the discussions in the same place.
|
|
#
?
Sep 22, 2019 18:45
|
|
|
Yeah, I don’t get the fetish for closing work items due to “age,” and I really don’t get not properly marking them as duplicates. I’ll look at a significant GitHub repo’s closed issues and see a whole bunch of reports closed because they’re duplicates of a fixed issue without being marked as such, just a comment like “fixed in 2.7” (or whatever). Instead just mark them dups of the actual fix, then everyone still sees that it was fixed, but you also can get an idea how prevalent the issue is.
|
|
#
?
Sep 22, 2019 19:57
|
|
|
I was just thinking "I’ve never really considered using fetch request templates, wonder how that works", so I’m clicking around the model editor and... there’s nowhere to specify sort descriptors? How is this useful? I guess it’s easier to gently caress up a predicate than a sort descriptor but really? Wonder what fraction of fetch requests are executed without sort descriptors. My bet is on "tiny".
|
|
#
?
Sep 23, 2019 00:26
|
|
|
Most people just cons up their fetch requests in code, the tools for fetch request templates have never really covered the full breadth of the API unfortunately. The nice thing is that you can use $VARIABLES in a predicate for a fetch request and just do the template thing yourself in code.
|
|
#
?
Sep 23, 2019 01:34
|
|
|
Makes sense I guess. Can’t help but wonder if there’s a chicken-and-egg thing there, where I’ll just make fetch requests in code because there are literally zero fetch requests I can fully construct using the editor.
|
|
#
?
Sep 23, 2019 02:02
|
|
|
Other than sort descriptors, do you (or anyone else) have any specific fetch request APIs you’re missing a lot in the tools?
|
|
#
?
Sep 23, 2019 04:27
|
|
|
That’s the big one, and it might be enough to push me from "why would I do this" to "nifty". I do set fetchBatchSize a lot, but that’s sufficiently device-dependent that I'd question its utility in the editor. Nothing else comes to mind.
|
|
#
?
Sep 23, 2019 05:26
|
|
|
I don't know if I hosed up something with our Apple Pay certs or our payment processor did, but I am having a BAD TIME. Edit: Also ended up figuring out I needed to manually delete the certs and provisioning profiles in the certificate repo to get fastlane to do what I wanted it to. I guess it's very useful when things aren't hella out of date. KidDynamite fucked around with this message at 03:08 on Sep 24, 2019 |
|
#
?
Sep 24, 2019 03:03
|
|
|
Well iOS13 has completely broken the dick off our Apps at work. Like, boss yelling at people broken. wtf is with that stacked Nav Controller? Also: Kill all bots. Except buildbot. I like that bot. And that bot on twitter that used to chase conservatives around demanding they fill out their detention paperwork for the FEMA death camp. That can stay too. duck monster fucked around with this message at 07:53 on Sep 25, 2019 |
|
#
?
Sep 25, 2019 07:50
|
|
|
I'm interested in building a fairly simple iOS app, but I have no experience in app development at all (I'm moderately proficient in programming). I was thinking of learning and then using react native. Should I learn any iOS development beforehand or can I just dive in with react native?
|
|
#
?
Sep 25, 2019 14:09
|
|
|
If you want to build a simple iOS app, you’re not doing some cross platform thing with major concerns about code reuse, just get the iOS SDK and make your app with Xcode.
|
|
#
?
Sep 25, 2019 17:12
|
|
|
duck monster posted:Well iOS13 has completely broken the dick off our Apps at work. Like, boss yelling at people broken. Please test your apps on the betas, that's what they're for.
|
|
#
?
Sep 25, 2019 18:49
|
|
|
|
| # ? May 16, 2024 00:11 |
|
|
brap posted:If you want to build a simple iOS app, you’re not doing some cross platform thing with major concerns about code reuse, just get the iOS SDK and make your app with Xcode. Well I was also hoping to use this to get more comfortable with javascript and node.
|
|
#
?
Sep 25, 2019 19:05
|
|