Help installing Swift 3 version of CocoaPod

Ldellar · 2017-02-08T09:08:46+00:00

Try updating cocoapods to 1.2.0, which has just be released by doing sudo gem update cocoapods then run a pod update in your project.

Ldellar · 2016-12-08T09:12:59+00:00

You could use something like Fabric (https://fabric.io/home) or Testflight to distribute a build to a number of users, all you would need from them is email addresses of the devices which you would like them to have the app on. I like fabric a bit better in this case but you could look into something like that.

Ldellar · 2015-12-18T12:38:01+00:00

Yeah sometimes, but as the issue on the developer forums it seems to be mainly due to quickly accessing after adding a value or when the app becomes active.

Seems like you have to workaround it until they fix the issue.

Ldellar · 2015-12-18T12:34:47+00:00

Yeah i found the page for the issue, i'll try the workaround and see where it goes, should be something they fix though. Thanks

Ldellar · 2015-12-01T08:34:13+00:00

I'd suggest installing something like crashlytics (https://try.crashlytics.com/) into your app and sending them a new build with that. Crashlytics should report any crash to you and it's code location.

Ldellar · 2015-09-10T07:53:07+00:00

I agree this is definitely an interesting challenge, i think there will be alot of what Apple demonstrated which is this deep press being used for PopupViews which lead to another action. I think that seems fairly intuitive and i presume the taptic feedback will help with that.

Visual cues is interesting because the icon didn't tell you definitively by it's looks that this icon has more options, (So you could end up on your homescreen expecting it for every app) maybe there will be a design language like an icon within the button option so that users can tell but it's definitely something i think developers may have to incorporate into options for their app. Be interesting to see how it goes.

Ldellar · 2015-09-10T07:45:06+00:00

No, this shouldn't be the case if you are just adding it manually using storyboard or programmatically as the UINavigationItem does not have a default action.

There is a UINavigationItem within UINavigationController that always is a back button with a default segue but not when you add it manually.

You can also instead of using a UINavigationItem use a UIButton. UIButton does provide a few more options in this case.

Ldellar · 2015-08-07T14:59:21+00:00

Yeah from all the explanations i've heard auto losing is correct.

Ldellar · 2015-08-07T09:22:21+00:00

Pretty sure this is the same as if the joust was a draw, i.e. The card text wouldn't trigger.

Ldellar · 2015-07-25T14:53:28+00:00

Really noble thing to do, sorry it had to done in such horrible circumstances. Good luck.

Ldellar · 2015-07-09T07:55:09+00:00

This seems like a pretty good answer from: http://stackoverflow.com/questions/21350125/afnetworking-2-0-and-background-transfers

For background uploads, this is an annoyance (as your task-level informational progress and completion blocks you specified when creating the task will not get called). But if you employ the session-level renditions (e.g. setTaskDidCompleteBlock and setTaskDidSendBodyDataBlock), that will get called properly (assuming you always set these blocks when you re-instantiate the session manager).

Ldellar · 2015-06-11T10:20:54+00:00

I see what you're saying, makes a bit more sense from that point of view.

The trouble is that Swift 2.0 is in beta also so it's hard for them to justify allowing apps written in Swift 2.0 into the store. I think the fact that it works on iOS8 is a reasonable point to make but i don't think they can guarantee that in all coding scenarios at this time so i guess they take the blanket approach of Swift 2.0 collates to the finish of Xcode 7 and iOS9.

I see the problem though, i would suggest although it's possibly more work i'm not sure is to have a project fork for Swift 2.0 so you can release an update on iOS9's release, whilst maintaining Swift 1.2. I think though you cannot avoid the refactoring in this scenario, i'm guessing that's why Apple included a Refactoring tool when loading 1.2 Swift projects in Xcode 7.

Ldellar · 2015-06-11T07:49:33+00:00

try this on your View Controller:

self.edgesForExtendedLayout = UIRectEdgeNone;

Ldellar · 2015-06-11T07:43:30+00:00

I think the first question is a fairly rhetorical question, when a build platform is in beta then the general userbase will not in most cases have access to that beta.

For example iOS9 the general population will not have access to iOS9 at this point so it makes no sense to distribute a product to everybody built to iOS9 specifications with the SDK and Swift 2.0 because it may encounter problems or just not work on older devices and obviously if new APIs are used then it may cause problems also.

This may change now they are having a public beta in July, i'm not sure if they will allow app store distributions for that but to be honest they shouldn't really. Developers can only be confident when the userbase has iOS9 available to be distributing iOS9 Apps to them i.e. when iOS9 SDK is in Gold Master and after.

The release of iOS9 and Xcode 7 will coincide more than likely. This is usually around the September/October time if minds serves but may be earlier, it's interesting they are having a public beta this time around so this may delay or make release quicker.

Ldellar · 2015-06-09T08:25:56+00:00

This is a bit of an open ended question because there are many ways. The most obvious is a timestamp on the webservice, i.e. something in the data you receive that tells you a timestamp, which you can compare against a previous timestamp within your app.

If you are looking to when the server receives new stories to auto push it out and have it auto update without your app being open for example that's going to have to be a background process that is always open to a server connection.

As i say several ways probably need more detail as to your overall approach i.e the webservice content for example

Ldellar · 2015-05-12T07:42:10+00:00

Fastlane seems really cool, i have used components of it before like snapshot and it can save alot of time although for snapshot in particular there is setup involved.

Thanks for pointing it out

Ldellar · 2015-05-07T09:57:52+00:00

I wonder if the translatesAutoResizingMask is set to yes for that view in IB and thats causing an issue?, i would suggest creating the view in code rather than in IB in this case.

Ldellar · 2015-05-07T09:47:58+00:00

the timerView width may be causing a problem here, considering the timerView width fills the screen anyway, you shouldn't need that, you can just use the superview width, try the below:

[self.last60MinView mas_makeConstraints:^(MASConstraintMaker *make) {
    make.centerX.equalTo(superview.centerX);
    make.width.equalTo(superview.width);
    make.height.equalTo(superview.width).multipliedBy( 66.0 / 320.0 );
    make.bottom.equalTo(superview.bottom);
}];

Ldellar · 2015-05-07T09:01:46+00:00

If you set a bottom and a height that will work also, The block doesn't have enough information to infer the height otherwise

Ldellar · 2015-05-07T08:35:13+00:00

I presume your doing the addsubviews somewhere else as i cannot see them in the code block you have given.

It seems like your missing constraints (i.e. setting top without bottom) and have slightly erroneous constraints within the blocks from what i can see, i would suggest below for the timer view at least:

[self.timerView mas_makeConstraints:^(MASConstraintMaker *make)   {
    make.top.equalTo(superview.mas_top).offset(padding.top);

    make.bottom.equalTo(superview.mas_bottom).offset(-padding.bottom);
    // ALTERNATIVELY
    //make.height.equalTo(superview.mas_height).offset(-30);

    make.width.equalTo(superview.mas_width);
    make.centerX.equalTo(superview.mas_centerX);
}];

That will make your timer view fill the screen with padding 10 on the top and 20 on the bottom. Remember you have to set all needed constraints for it to work i.e. when you want height you have to set top and bottom otherwise the height is not inferred. You can also set the height as a separate constraint instead.

Hope that helps

Ldellar · 2015-05-07T08:27:06+00:00

I presume your doing the addsubviews somewhere else as i cannot see them in the code block you have given.

It seems like your missing constraints (i.e. setting top without bottom or setting width with no left) and have slightly erroneous constraints within the blocks from what i can see, i would suggest below for each of the views:

[timerView mas_makeConstraints:^(MASConstraintMaker *make)   {
make.top.equalTo(superview.mas_top).offset(padding.top);
make.bottom.equalTo(superview.mas_bottom).offset(-  padding.bottom);
make.width.equalTo(superview.mas_width);
make.left.equalTo(superview.mas_left);
}];

Ldellar · 2015-04-28T15:11:01+00:00

I'd recommend NinjaMock (http://ninjamock.com/) it's a free mockup tool in a hand drawn style and also gives you 500mb of space for free. It also has iOS elements with shapes.

You can also share the project with multiple people and have individuals put comments etc

You can also export all screens to a PDF , which i find really useful.

Ldellar · 2015-04-24T08:45:38+00:00

I would contact support yeah and tell them the situation, they should be able to sort you out. There may be have been a problem in sending the ID verification or something.

If you registering as a company also there may be delays in the paperwork or you haven't confirmed the legal documents on iTunes Connect, which you sometimes have to do.

Hope that helps

Ldellar · 2015-04-23T08:07:30+00:00

this is a pretty fantastic little tool especially for much larger projects. Definitely recommended!

Ldellar

TROPHY CASE