Flickr App shows no iOS 12 AutoFill into?

wkleem

How is this even possible? No login info appearing for AutoFill in iOS 12 for Flickr. The login is saved in 1Password and doesn’t appear where it should? Pasting works here.

The Microsoft login has issue too. The wrong info is there for home and iCloud. Only 1Password is available for AutoFill.

ag_ana

No login info appearing for AutoFill in iOS 12 for Flickr.

What is the URL for your Flickr item inside 1Password?

The Microsoft login has issue too. The wrong info is there for home and iCloud. Only 1Password is available for AutoFill.

I don't think that what you are seeing in your second screenshot is coming from 1Password though. I think that's just iOS showing you a list of the email addresses you use (I might be wrong, but I think it takes these from your Contacts app).

wkleem

Hi ag_ana,

For Flickr, the website is https://identity.flickr.com. There is nothing to click on, no (key) Passwords, no indicator at all.

The initial screens I see are what I have shown from the Flickr app and from Microsoft’s OneDrive app with the text box active.

I assume AutoFill will make use of the Microsoft site address? I don’t have a contact for Microsoft or any of the logins. All of them are in 1Password.

iOS AutoFill confuses me. I don’t know where the Microsoft login listed email is coming from. I use a different email.

AGAlumB

That's really odd. I thought Flickr was owned by Yahoo. Anyway, I just downloaded it on my iPhone to try. It looks like their app isn't using standard iOS APIs for this at all, much less having been updated for iOS 12 and Password Autofill. I wonder if this is just a wrapper around a webview. The only solution is for them to update their app using the appropriate developer tools and according to Apple's guidelines.

wkleem

Flickr is now owned by Smugmug who purchased it from Verizon. Verizon purchased Yahoo and Flickr among other Brands which went with the purchase.

Flickr for the web works but not their app. Thanks for looking into the matter.

Even under Yahoo, it was neglected for years. Yahoo purchased Flickr 14+ years ago, in 2005

AGAlumB

Ahh glad I am not losing my mind, but clearly I haven't kept up with all of that. Glad to hear the website is more accommodating at least, and hopefully they'll fix their app. In the mean time, the 1Password for iOS Quick Copy feature can help:

1. Open 1Password
2. Copy username
3. Switch to and paste it
4. Switch back to 1Password to auto copy the password
5. Switch back and paste to login

Cheers! :)

wkleem

Thanks for your help. It surprised me to find a part of my workflow that was not keeping up with iOS. It was updated one month ago to Flickr v4.12.2.

Compatible with iOS 9.3 or later. I assumed Password AutoFill would work because I am on iOS 12.4 not what the compatibility is?

Now the about Microsoft issue...

AGAlumB

It's a matter of the app following Apple's guidelines. I don't know the specifics off hand, but there aren't a lot of apps around nowadays that support iOS 9, and doing so means not taking advantage of the latest tools from Apple, which I have to think at least plays a part in them not supporting Autofill. 1Password 7 became iOS 12-only because we wanted to take advantage of the new stuff, and it wasn't feasible to support the old simultaneously. There are many frameworks used now which did not even exist in iOS 9, and 10. Apple started laying the groundwork for Autofill in iOS 11 with iCloud Keychain, but it didn't expand to allow 3rd party apps like 1Password to integrate with it as providers until iOS 12.

wkleem

Thanks. The downside is, with phones/devices getting more costly, I just want to use older devices. I'll have to look for a new device post iOS 13+/iPadOS.

ag_ana

I see what you mean. Luckily, it has more to do with operating system version than the device itself ;)

wkleem

I apologise if there is any confusion. I don’t want to spend the money unnecessarily and I have a potential big purchase coming : Moving to Catalina and 1Password 7 for the MAC or stay with Windows and get a new PC or run Parallels (VM) within the MAC. Waiting for September 2019.

There is a time limit. Take iPhone 7, a 2016 model. If I were to get one now I would have missed out 3 years out of maybe 5 years and Agilebits isn’t extending the OS compatibility backwards. I am one of those stragglers who won't part with old devices.

Best to get a device early in its life cycle to make the most out of it. It might have been more costly purchasing the iPhone 7 in 2016.

When it comes to subscription:
The current 1Password version OS, is now at iOS 12. When iOS 13 is released 1Password 8 will be for iOS 13, and unlikely for a prior OS (12) plus iOS 13. For 1Password, it was iOS (an earlier release), now iOS 12 and it will iOS 13+ eventually.

It will work but I could be locked out? I was denied before when I attempted to use a iOS 10 1Password (32bit) device side-by-side with newer iOS 11 1Password (64bit) devices. 32bit OS is now dead.

Subscriptions were first made available in 2015. Few 2015 devices now work with the current 1Password subscription before year end when iOS 13 is released, iPhone 6 and iPhone 5s won’t make the cut. Apple has moved on with FaceID etc.

https://support.1password.com/system-requirements/

1Password system requirement is subject to change. Windows 7 EOL is in 6 months and I am a Win7 user.

A phone can in theory last 5 to 6 years and often it would be upgraded after 2 to 3 years. There could be a new, like the iPad Mini 5, a similar low cost phone coming with a 4 year interval in 2020l. The current Mac Mini also had a 4 year interval between release, 2014 to 2018.

Thanks.

AGAlumB

Best to get a device early in its life cycle to make the most out of it. It might have been more costly purchasing the iPhone 7 in 2016.

I couldn't agree with this statement more. It's definitely an investment upfront, but while I've bought some "old" phones at times, I've definitely gotten a lot more value from the ones I bought while they were still the latest model. For example, I bought an iPhone 7 when the iPhone 8 was released. It was cheaper, but not by a lot. Not something I regret, but it's showed its age much more quickly than if I'd got the latest model.

The current 1Password version OS, is now at iOS 12. When iOS 13 is released 1Password 8 will be for iOS 13, and unlikely for a prior OS (12) plus iOS 13. For 1Password, it was iOS (an earlier release), now iOS 12 and it will iOS 13+ eventually.

1Password 8 hasn't even been announced, so I don't know that it's useful to speculate about its requirements. Ultimately it depends on if there are things we need to give up to support the latest OS features, as that makes it harder (or impossible) to maintain backward compatibility.

As far as 2015 devices, iPhone 6S and SE were still being manufactured until just under a year ago, and remain supported by iOS 13. Same goes for iPad Pro (1st generation) and iPad mini 4. I think the 2014 iPad Air 2 may be the oldest device supported by iOS 13. iPhone 7 and 8 are still in production, at least for now, so I'd expect them to work with iOS 14 as well, though that remains to be seen. There's a lot of mileage that can be gotten out of these devices even before they are no longer supported by Apple. But there are limits.

wkleem

Best to get a device early in its life cycle to make the most out of it. It might have been more costly purchasing the iPhone 7 in 2016.

I couldn't agree with this statement more. It's definitely an investment upfront, but while I've bought some "old" phones at times, I've definitely gotten a lot more value from the ones I bought while they were still the latest model. For example, I bought an iPhone 7 when the iPhone 8 was released. It was cheaper, but not by a lot. Not something I regret, but it's showed its age much more quickly than if I'd got the latest model.

That's what I dislike about tech. It mostly seems to age faster that anyone expects! The CPU Throttling "Batterygate" of the iPhone 6s, 6s Plus and SE models didn't help.

Coming back to the original post, iOS 9 is definitely unsupported. No working around it and the implementation of iOS AutoFill is uneven, or unreliable. I can only hope things improve with iOS 13.

wkleem

@brenty,

As you have the iPhone 7, or even for some earlier or later iPhones, watch out for Batterygate as, when the iPhone 6s issue surfaced, the iPhone 7 was too new to be affected by it and Batterygate can show up eventually.

https://insider.com/apple-batterygate-how-older-iphones-slowed-down-and-why-its-a-big-deal-2017-12

""Last year we released a feature for iPhone 6, iPhone 6S and iPhone SE to smooth out the instantaneous peaks only when needed to prevent the device from unexpectedly shutting down during these conditions. We've now extended that feature to iPhone 7 with iOS 11.2, and plan to add support for other products in the future.""

AGAlumB

I think Apple could have handled it better initially, but they seem to have learned from the experience and I'm rather fond of the battery info in Settings now that resulted from that. It's allowed me to know to get a replacement when it became a problem. I'd rather have my phone shut down than overheat or worse, but getting a new battery is even better -- almost as good as getting a new phone in many cases -- and not that expensive. :)

wkleem

There is no resolution to my reported issue then? Based on reports on the Agilebits Discussion Forum, iOS AutoFill, it seems, is known to be unreliable at times as well.

https://discussions.agilebits.com/discussion/106569/ios-auto-fill-is-unreliable#latest

You’ll need to login, perhaps use the app, then put it in the background and come back to it later and try yet login using 1Password’s auto-fill integration with iOS.

Might as well try it out. So far, Flickr was in the foreground when I noticed the issue. Or in the background briefly, long enough for Duo Prompt with 1Password 7 to work.

Thanks

AGAlumB

@wkleem: I haven't seen evidence that Autofill is unreliable. Rather, apps that don't properly support Autofill have issues. They'd need to update their apps in that case. It isn't something we or Apple can force them to do (though it's possible Apple may remove older APIs in the future which would have the effect of requiring apps to use only the new ones, which could theoretically help). So, for the time being at least, the only options are for you to work around the Flickr issue, and encourage them to update their app.

wkleem

Thank you. Some developers are difficult to reach even with their forums. Flickr was one of those. Issues which went unsolved for months.That was during the Yahoo owned days and Verizon also. Smugmug, the new owner inherited a mess from Verizon.I can only hope for the best for improvements.

Agilebits should be commended on their support. Vanilla Forum Software not. :lol:

AGAlumB

Thanks for the kind words! We're not perfect, but we try our best -- and hope for the best when we're stuck waiting on others as well. :lol:

wkleem

With the release of iPadOS, I am hopeful that because iOS apps might/will not work on the iPad after iPadOS release I won't see this Flickr issue on the iPad although it would persist on the iPhone (x) Plus/Max? Shouldn't be long now!

Flickr will have to release a Flickr for iPad app.

I've had a thought that perhaps Flickr is a web mini browser made to look like an app? It might partly explain why it would not work. I've no way to confirm my suspicions.

AGAlumB

Yeah, I think that's pretty much what they're doing. But it can be hard to tell for sure.

I wouldn't count on them releasing a new iPad app, but it sure would be nice. There are a few I'd like to see myself. :)

wkleem

I don’t use 1Browser and tried to iOS AutoFill in 1Browser - www.Flickr.com.

It isn’t absolutely certain but iOS AutoFill does not work with a browser inside an app. Or maybe also Chrome or Firefox etc. I have not tried those.

Try 1Browser with iOS AutoFill. It does not work.

There is still an advantage to keeping the 1Password AutoFill for Browsers and 1Browser as they are dependable, however slightly so please don’t remove this functionality.

wkleem

@brenty,

Only Mobile Safari works with iOS AutoFill, no alternate browsers work - Chrome, Firefox, 1Browser - , from my testing of www.flickr.com.

AGAlumB

Whether to not Autofill works in that context depends on how the app has implemented their in-app browser and the way the website being loaded it in is designed, I'm often able to use iOS Password Autofill within apps' built-in browsers, but certainly not in all cases.

wkleem

Thanks. I rarely go outside of Mobile Safari and decided to do so for Flickr. I should try out other sites.

A hard part of iOS is that it isn’t multi user and my phone is like a family phone. It gets passed to other people. No way around it.

Ben

:+1:

Ben

wkleem

Installed iOS13.1 and iPadOS.

iOS 13.1 has made it harder to use 1Password 7.4.1 on my iPhone SE. 1Password 7.4.1 which had a bigger lock icon with under iOS12.4.1 was fine. I updated to iOS 13.1 and now the Master Password field is nearly almost covered by the keyboard consistently. E.g. From identity.flickr.com

AGAlumB

Indeed. Considering that Apple discontinued the iPhone SE last year prior to the release of iOS 12 and no longer makes any phones that size, I'm not terribly surprised they are no longer designing the OS around it. The keyboard has definitely grown in size over the years to add features as the average screen size has grown.

wkleem

Hi
I noticed the difference in 1Password prior to v7.4 and v7.4+. 7.3 and earlier had a smaller lock icon. v7.4 has a larger lock icon.

I wasn’t bothered until IOS 13 appeared, which was when the blocked Master Password issue, if it happened with iOS 12.x it was random and now it isn’t.

I am hopeful for another device for us small screen users. It could be out in 2020. The predictions so far have been wildly inaccurate!!

AGAlumB

Yeah I really thought Apple would release another small phone last year. I guess we'll have to wait and see. We need to prioritize designing the UI for current devices, but as we continue to iterate on it perhaps we can find something that will will work better.

wkleem

It isn’t just the iPhone SE now? I noticed with iPad Mini 5 and iOS 13.1.1 the same covered up Master Password is happening? It shouldn’t be happening.

I clicked on the Password “key” icon in iOS AutoFill.
1Password ... (For the sites which show AutoFill)

Flickr still doesn’t work properly. On the iPad with iOS 13’s one handed (Floating) keyboard, it mitigates the issue of the Master Password field being blocked. I suggest getting familiar with the iOS 13 new keyboard options.

1Password Extension works properly from Mobile Safari.