|
So I uploaded a new build to itunes connect and I can't see any of my builds. The apple system status page says everything is ok with itunes connect. Is this just normal Itunes Connect fuckery? Maybe check back in the morning? edit:n/m i'ts fuckery TheReverend fucked around with this message at 07:14 on Aug 24, 2015 |
#
?
Aug 24, 2015 06:47
|
|
|
|
| # ? Jun 7, 2024 06:36 |
|
|
Gotta wait a couple minutes.
|
|
#
?
Aug 24, 2015 08:58
|
|
|
Could be. I usually see my uploaded build on the prerelease page within seconds with the status "uploaded", but getting an odd delay would not surprise me.
|
|
#
?
Aug 24, 2015 12:51
|
|
|
epalm posted:Congrats! How long between approval and app store availability? Thanks! It took a little over 24 hours to show up.
|
|
#
?
Aug 24, 2015 21:53
|
|
|
Ugh. I cannot figure out how to get the signing to work right. We wrote a phonegap app, and this is one of my first times on a Mac and XCode. I've found my way around and built the app. I bring it into GapDebug and it says that it needs developer signed. I thought I did that already! In the XCode preferences under accounts I see my account with provisiong profiles. I select those profiles in the Build Settings page for the project. Still doesn't work right. I'm reading everything I can about this, still not sure what I'm missing. I'm going back through this thread to see if there is something in there to help but if anyone has a suggestion it would be much appreciated.
|
|
#
?
Aug 26, 2015 19:38
|
|
|
KoRMaK posted:but if anyone has a suggestion When you write a phonegap app you deserve all the trouble you get
|
|
#
?
Aug 26, 2015 19:45
|
|
|
UIApplication posted:When you write a phonegap app you deserve all the trouble you get It worked fine with the android build 
|
|
#
?
Aug 26, 2015 19:52
|
|
|
KoRMaK posted:It worked fine with the android build This in a nutshell is why phonegap is bad Are you signed into multiple appleids in Xcode preferences? Xcode 6 is kinda wonky when it's deciding which set of certificates to use when signing a build.
|
|
#
?
Aug 26, 2015 20:19
|
|
|
Anyone else running Google Ads get asked to disable ATS in their whole app?
|
|
#
?
Aug 27, 2015 16:28
|
|
|
UIApplication posted:This in a nutshell is why phonegap is bad The code signing was an issue I figured out by trying a couple things but I'm not sure which one exactly did it. I was able to validate the package though! And the app is in itunesconnect! The one step I had to do was create an App ID, I think that probably cleared up most the issues.
|
|
#
?
Aug 27, 2015 16:31
|
|
|
How the gently caress do I animate a UIView's frame with the UIView.animateKeyFrames? A frame isn't directly animatable, but I can animate a layer's bounds, anchor and position? Does anyone have a solid reference to how the anchor and position correlate to a CGRect? I feel like I've done this before and now I'm angry at myself 
|
|
#
?
Aug 27, 2015 16:38
|
|
|
Doh004 posted:How the gently caress do I animate a UIView's frame with the UIView.animateKeyFrames? A frame isn't directly animatable, but I can animate a layer's bounds, anchor and position? Does anyone have a solid reference to how the anchor and position correlate to a CGRect? https://github.com/facebook/AsyncDisplayKit/blob/master/AsyncDisplayKit/ASDisplayNode.mm#L627-L647
|
|
#
?
Aug 27, 2015 16:46
|
|
|
Doctor w-rw-rw- posted:It doesn't account for transform, and I don't advocate adopting ASDK, but once upon a time I wrote transformation code for ASDK, which might help as a reference: Awesome, thank you! 
|
|
#
?
Aug 27, 2015 16:53
|
|
|
A lovely surprise today one of our apps was sold as a white label solution to another company, we will be handling distribution and modifying the code. Now, after the fact they are asking Devs for things we consider going forward (like distribution etc) what are somethings I should point out? I've already got things like: Maintenance Updates New Features Configuration Managing the other companies Appstore account. etc Oh and by the way you have 2 months to repackage the app for them (they don't even have a backend!)
|
|
#
?
Sep 3, 2015 21:15
|
|
|
UIApplication posted:This in a nutshell is why phonegap is bad I think that it was because I didn't create a App ID in itunes connect.
|
|
#
?
Sep 3, 2015 21:17
|
|
|
I got an unfortunate email from an applebot: quote:Missing Push Notification Entitlement - Your app appears to include API used to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement. See "Provisioning and Development" in the Local and Push Notification Programming Guide for more information. If your app does not use the Apple Push Notification service, no action is required. You may remove the API from future submissions to stop this warning. If you use a third-party framework, you may need to contact the developer for information on removing the API. I don't even know how to use their push notification thing. I'll probably be fine ,right?  Anyone else gotten this before?
|
|
#
?
Sep 3, 2015 21:30
|
|
|
TheReverend posted:I got an unfortunate email from an applebot: Yes, I got it! If you look closely it says that if you don't give a poo poo about the error then you can ignore it. Which is what I'm doing!
|
|
#
?
Sep 3, 2015 21:32
|
|
|
Yeah that's what I planned on doing too I just wanted to make sure I really could ignore it. So yeah...gently caress it! Thanks!
|
|
#
?
Sep 3, 2015 22:01
|
|
|
TheReverend posted:I don't even know how to use their push notification thing. I'll probably be fine ,right? Check your provisioning profiles. I submitted an app without issue, then changed its bundle id and submitted it as a new app (for another college) and got that error. I went to Register iOS App ID, added the new bundle id and downloaded/installed a new provisioning profile and when I resubmitted I got no error.
|
|
#
?
Sep 4, 2015 00:25
|
|
|
TheReverend posted:I got an unfortunate email from an applebot: The only thing that'd go wrong here is that push notes won't work, so if you're not using them on purpose you're good
|
|
#
?
Sep 4, 2015 08:04
|
|
|
What system is currently suggested for private beta testing when it is absolutely imperative that we support anything as old as iOS 6.1? The system we're currently using is quite manual in its operation.
|
|
#
?
Sep 6, 2015 08:06
|
|
|
Crashlytics Beta plus a build script? (It's a bit finicky to set up if you don't want to have to install the lovely Crashlytics app everywhere, but then you're golden.) Also any instance of "Crashlytics" above may now be "Fabric", I haven't been keeping up with the pointless branding changes.
|
|
#
?
Sep 6, 2015 14:42
|
|
|
pokeyman posted:Also any instance of "Crashlytics" above may now be "Fabric", I haven't been keeping up with the pointless branding changes. This is, what, the 20th tech product called "fabric"?
|
|
#
?
Sep 6, 2015 17:41
|
|
|
Fabric works ok for me
|
|
#
?
Sep 6, 2015 18:16
|
|
|
kode54 posted:What system is currently suggested for private beta testing when it is absolutely imperative that we support anything as old as iOS 6.1? The system we're currently using is quite manual in its operation. HockeyApp (I think works for iOS 6? I don't see why it wouldn't)
|
|
#
?
Sep 7, 2015 15:11
|
|
|
kode54 posted:What system is currently suggested for private beta testing when it is absolutely imperative that we support anything as old as iOS 6.1? The system we're currently using is quite manual in its operation. If there's one thing you can absolutely get away with on Apple platforms, it's dropping older devices. We only support one major release back, and actually decided to drop iOS 7 slightly early to let us start using frameworks. It helps that Apple hasn't been dropping older devices with OS releases.
|
|
#
?
Sep 7, 2015 18:25
|
|
|
The problem with dropping older devices is that the lead developer personally owns several of them, and wants his app to work on them. Which it does. In fact, it works almost flawlessly. The only development issue he's experienced supporting as old as 6.1 was the one time he ran into a missing SDK function on link, that I helped him to discover was due to one or two of the static libraries in the workspace being built with iOS 8.x as the minimum target instead of the correct 6.1. He has also written an Android port, which is mostly functional, but misses half of the decoders I added to the iOS version. And he is also working on a Windows Phone 8.1 port, which has been terrible fun. One of the tricks he had to pull, that may get him restricted from the Windows Store, is that he couldn't figure out a way to keep his background audio process alive during screen locks and such, and resorted to instantiating the MediaPlayer framework and making it play a looping silent sample while his player is doing its own playing. At least Android and iOS provided means for a process to run in the background while playing audio. I'll see if I can post something to a WP topic about it.
|
|
#
?
Sep 9, 2015 02:37
|
|
|
Does Apple pay developers to have their apps ready for new poo poo like tvOS or whatever the latest iDevice is, like the people who demo their apps at Apple events? Or is it more like "you're lucky we're giving you access to this" and it's just part of the biz to have your poo poo up and running on the latest and greatest?
|
|
#
?
Sep 9, 2015 19:25
|
|
|
Exposure and early access are worth a lot of money. One of the reasons WWDC used to be very important (early access)
|
|
#
?
Sep 9, 2015 20:12
|
|
|
Yeah, you get early access w/ hands-on help and potentially a decent amount of screen time in the event. You also get the experience of being trapped in a box in Cupertino for a few days not allowed to touch your company's repos. If you're talking about devs in general, they're mostly just hoping to get the "Apps That Do <New Thing>" app store features/tech article boost.
|
|
#
?
Sep 10, 2015 18:33
|
|
|
We released (some of) the tools we use to manage multiple iOS simulators and run automated tests in parallel, which may be of interest to some of the folks in this thread: https://github.com/facebook/FBSimulatorControl
|
|
#
?
Sep 10, 2015 19:21
|
|
|
Subjunctive posted:We released (some of) the tools we use to manage multiple iOS simulators and run automated tests in parallel, which may be of interest to some of the folks in this thread: https://github.com/facebook/FBSimulatorControl Ew, reverse-engineering internals.
|
|
#
?
Sep 11, 2015 21:40
|
|
|
eschaton posted:Ew, reverse-engineering internals. Well, they exhausted all the helpful approaches provided by Apple. Caveat emptor, but as with xctool it works for us in large-scale production. We've been asked for it so many times since we first mentioned that we had a tool for it. Apple doesn't seem to care at all about programmatic control of their developer tools (I miss you, Shark API), which I find surprising. Running automated tests in parallel is hardly an esoteric thing, and they'd no doubt benefit from it internally.
|
|
#
?
Sep 11, 2015 22:00
|
|
|
eschaton posted:Ew, reverse-engineering internals. I mean, it'll probably never happen, but one can dream.
|
|
#
?
Sep 11, 2015 22:18
|
|
|
Subjunctive posted:Well, they exhausted all the helpful approaches provided by Apple. Caveat emptor, but as with xctool it works for us in large-scale production. We've been asked for it so many times since we first mentioned that we had a tool for it. So much this and apple release/test tooling in general. I think this explains a lot about how release tooling and code quality for the apple ecosystem is so far behind most every other platform and how iOS developers have a bad reputation with respect to a testing culture (slowly changing). I always say at work that Apple can't possibly dogfood this stuff it just doesn't scale past toy apps, and is/was to unstable. If you deviate from their ecosystem you have to be willing to devote time to fixing everything between releases or waiting for someone else to fix it between releases (see xctool between Xcode 5 and 6) meanwhile your CI/CD systems are down when you need them most between releases. I won't even talk about things that happened at WWDC when I showed some of these issues to their Dev Tools team in person. The response was basically: ¯\_(ツ)_/¯ I think the quote paraphrased: "I know that sucks, and that situation sucks, but I think it's fixed in the next release try the alpha" I guess they are slowly trying to make it better and make it easy but at one release a year at a time...?
|
|
#
?
Sep 12, 2015 00:50
|
|
|
Subjunctive posted:Apple doesn't seem to care at all about programmatic control of their developer tools (I miss you, Shark API), which I find surprising. What makes you think so? Just keep in mind, as you answer, that there are always lots of things to do that need to be prioritized…
|
|
#
?
Sep 12, 2015 04:44
|
|
|
Kallikrates posted:So much this and apple release/test tooling in general. I think this explains a lot about how release tooling and code quality for the apple ecosystem is so far behind most every other platform and how iOS developers have a bad reputation with respect to a testing culture (slowly changing). There are a lot more releases than one a year. Xcode 6.0 was beta at WWDC 2014, and the most recent GM release is Xcode 6.4 which came out at WWDC alongside the first Xcode 7 beta. There's an Xcode 7 GM Seed available, and an Xcode 7.1 beta with iOS 9.1 and tvOS support too. Also, Apple dogfoods the tools plenty, including Xcode, and on large projects too. Many difficulties tend to come from an impedance mismatch between how some developers might want to work, and how the tools are designed to work. For example, there are lots of people who try to build frameworks or libraries for multiple platforms—like iOS and iOS Simulator—in a single binary. The tools and platform simply aren't designed for that, and anything that tries to fight the tools on that will be fragile. (As an aside, they break even more spectacularly when we do things like add new platforms that use the same CPU architectures, like say iOS and tvOS. Maybe there's a reason I've been trying for a while to warn people away from building multi-platform framework binaries…) Similarly, when third-party tools like xctool rely on reverse-engineering to accomplish their goals, it shouldn't surprise you when they break between even individual fix releases. Plug-ins built via reverse-engineering are in the same boat; neither of these are likely to be considered when working on changes. (And scripts that purport to "update" plug-ins for new Xcode versions by tweaking their Info.plist are pure evil, never ever use them.) What kinds of issues did you bring to the Xcode lab this year? Keeping in mind that nobody there can help with reverse-engineering, and nobody can say even the vaguest thing that could be construed as to involve future plans or promises.
|
|
#
?
Sep 12, 2015 05:02
|
|
|
eschaton posted:There are a lot more releases than one a year. Xcode 6.0 was beta at WWDC 2014, and the most recent GM release is Xcode 6.4 which came out at WWDC alongside the first Xcode 7 beta. There's an Xcode 7 GM Seed available, and an Xcode 7.1 beta with iOS 9.1 and tvOS support too. ...Thus, to quote Kallikrates, explaining a lot about how release tooling and code quality for the apple ecosystem is so far behind most every other platform and how iOS developers have a bad reputation with respect to a testing culture. Apple makes a decent IDE but it just can't do everything. Okay, so IntelliJ is closed source, as is Visual Studio, and are proof that a closed-source IDE can thrive. Apple will never open-source Xcode (  ), because it develops impressive new development tools tightly integrated with the target hardware and software SDK behind closed doors, and releases it in bursts.However, Xcode doesn't provide a public SDK, so useful plugins that are both necessary for some and not necessarily suitable for inclusion in the base IDE are either not available or require significant reverse engineering. Developers need this so much they created Alcatraz and an entire ecosystem dedicated to providing what Xcode can't. Arguably, CocoaPods exists for the same reason - Apple dragged their feet on offering decent support for libraries for many years after the need to pull in external dependencies was obvious, and it still is only just kind of okay. In the absence of a useful Xcode plugin API, which for some reason Apple is unwilling or unable to accommodate, reverse-engineering is the only way outside of Apple to move development against Apple platforms forward down avenues that Apple does not yet understand or find useful enough to pursue. Fixing breakage is easier than asking, waiting, hearing nothing, and possibly never receiving. tl;dr Apple's dogfood coverage simply cannot and does not reach 100%, and has some major blind spots.
|
|
#
?
Sep 12, 2015 05:22
|
|
|
I can understand Apple not wanting to get locked into a public plug-in API. And a developer making a choice to delve into dependency hell is, IMHO, that developer's problem. It's not Apple's job (or any IDE's job, really) to manage your 3rd party dependencies for you. edit: that includes reverse-engineered plug-ins.
|
|
#
?
Sep 12, 2015 05:36
|
|
|
|
| # ? Jun 7, 2024 06:36 |
|
|
Doc Block posted:I can understand Apple not wanting to get locked into a public plug-in API. Doc Block posted:And a developer making a choice to delve into dependency hell is, IMHO, that developer's problem. It's not Apple's job (or any IDE's job, really) to manage your 3rd party dependencies for you. /grump
|
|
#
?
Sep 12, 2015 05:57
|
|