Yes, it will work as before.
The qrscanner plugin came to crash.
– iOS9
CoronaSDK-2883 : Available.
CoronaSDK-2948 : Available.
CoronaSDK-2951 : Available.
CoronaSDK-2961 : Available.
– iOS10
CoronaSDK-2883 : Available.
CoronaSDK-2948 : Crash.
CoronaSDK-2951 : Crash.
Crash report > https://goo.gl/zFMZEx
CoronaSDK-2961 : Crash.
The crash happens at the timing of dialog indication of camera permission.
Is it possible to settle this problem?
CyberCatfish, gah, iOS 10.
Try this. In build.settings add this key to iphone -> plist
NSCameraUsageDescription = ‘Used to scan QR codes and barcodes’
That is actually required for all new iOS 10 apps.
I don’t get the QR scanner to work with my iPad running iOS9.3.
build.settings attached
Corona SDK v2016.2951
XCode 8
I get the following line in the log when trying to start the scanner:
Warning: Attempt to present <QRScannerViewController: 0x19c38f20> on <AppViewController: 0x160e3c00> which is already presenting <CustomAlertController: 0x168b0600>
Thank you [member=‘Lerg’];
I could settle a problem.
That execution of this setting I didn’t notice participates.
Setting was argued here and I knew. >> #65510:iOS10&xCode8
Therefore I made it the following setting.
NSPhotoLibraryUsageDescription = "Not used in this app", NSCameraUsageDescription = "Used to scan QR codes and barcodes",runewinse, I’ll check that a bit later.
CyberCatfish, thanks for sharing! I’ll add it to the docs.
Hey everybody,
I created QR generator library for Corona and thought that relates to this topic ;)
Check out the original post here:
https://forums.coronalabs.com/topic/65821-qrgenerator-for-corona/
And dowload it here:
runewinse, I couldn’t trigger the same error. So I think this could be due to your app code. Are you showing any alerts using native.showAlert()?
torbenratzlaff, nice! Now we can use one corona app to display a QR code and another one to read it. You can build a file transfer app this way, heh.
Also, a heads up for you guys. The plugin will become paid on Wednesday (Oct. 12). If you have any apps near completion, submit it while the plugin is free.
The plugin will be for sale for $14.99 for a week and $19.99 after that. Subscription based, to make sure I have resources to support it.
It was free for more than a year, I hope you enjoyed that little bonus.
As a matter of fact I do.
Exactly what does this mean? What happens after Oct 12 to existing apps using QR Scanner? Will they work, but cannot be updated without paying?
And is those $19.99 a one time fee or is it yearly?
For all of us that does not make a dime on our apps a one time fee is bearable, a yearly fee is not.
runewinse, probably you display an alert before invoking the scanner, which blocks it.
Existing published apps will work fine after Oct 12. But for an update the plugin has to be purchased.
I’d love to charge only once, but the subscription is the only viable choice for me to continue supporting the plugin, I’ve invested a lot of time in this plugin already. There are simply not so many users of the plugin, unfortunately.
Sorry for the inconvenience.
Thanks Lerg 
I thought about using both, generator and scanner in one app, to share data with another phone for example.
Could be used for user generated content (levels, images), preferences or even things like joining a local network.
Concerning the fee for the scanner, I think its fair.
@runewise as the lifetime of most unpaid apps is a year or less, it should be kind of a one time purchase, if you only use it for an existing project.
It would have been even fairer to mention from the start (*) that it would turn from free to a yearly subscription from the beginning. For some reason I had expected that free plugins would remain so so at least existing apps would’t be broken.
And broken they will be, as there is always some bug that needs attention and the app must be rebuilt/distributed.
It’s fair enough that Lerg wants to get paid for further dev/support, but I think the plugin in its existing shape/form/version could be free and all further development (and support for that matter) could be done on a paid version.
But what do I know. Well, well. I’ll be starting to dismantle the QR and NFC parts of my app tonight then. I’m not going to pay people to use my apps. I still have some pride left :D . And QR/NFC is more of a nice to have part anyway…
Maybe I’ll get back to QR/NFC if I win the lottery and the app actually takes off :rolleyes:
(*) WAS it mentioned from the start? I certainly didn’t catch that particular info if it was.
I do see your point in wanting to know from the start, that you use may cost something in the future. But sometimes plans change. Your suggestion of making the existing plugin for free and all updates not may work for other plugins, but as there are not many features that can be added to a QR scanner, that potential is pretty low.
Also I think you are over dramatizing, you don’t need “to win in a lottery” to be able to pay 20$ a year. I understand that you might think that the functiality is not worth its costs, but that questions why you put in such a worthless feature in the first place 
Paid plugins was the goal from the very beginning, that’s the reason I made them. They were free just because the payment system wasn’t built for them until recently. If asked, I always told people that the plugins will become paid eventually. I mentioned that in Corona Geek for sure several times.
Sorry for that not being clear.
I think a small sum accounting is sound for supply of continuous service.
There are several functions which have disappeared already in Corona, and I have the experience which would be a problem.
I think there are a lot of people who think they charge and want those functions, too.
I also want the place where I wish for the function in Corona and look for.
Even if the first order becomes a little expensive, I wish for that.
I don’t need to win in a lottery to be able to pay $20 a year. The lottery reference was to the chances of actually making enough money on an app to pay for the expenses making it. Unfortunately, for most people the chances are slim.
http://www.zdnet.com/article/think-your-app-is-the-road-to-riches-chances-are-youre-very-very-wrong/
The app that I’m working on now I use 6 plugins. So it’s not $20 a year. It could very well end up with $120+ a year just for plugins. I don’t need to win at the lottery to pay $120 a year either, but it’s starting to hurt a bit. And if it is Coronas future plan to move more and more (existing? new?) functionality over to plugins I will hurt more.
Worthless? Absolutely not! I find Lergs plugins very useful. But there is quite a difference between $0 and a running expense of $20 per year. Especially when you have to time that with the number of previously free plugin that you have mixed into your code. So some of them are not worth the cost for me at this point.
I certainly mean that it’s fair that developers want to get paid for their work. I too want that… :rolleyes:
My issue is that I though free was free. I certainly knew that the plugin marketplace was supposed to include paid plugins in the future, but I thought that was for new plugins.
As it turned out nothing is “safe”. Things can suddenly start to cost you money, and it’s not a one time cost either. It’s something that will keep on costing you.
The big difference between these ex-free plugins and, say, paint.net (a free paint tool) is that if paint.net decided to go from free to paid, the old version would still work. And even better, the images used with the old version would still work…
With plugins going from free to paid it’s a completely different story. Now integrated parts of your code suddenly stop working (*) unless you pay a yearly fee. You’re completely at the whim of the plugin developer. What if you have made an app that becomes useless without the plugin and the plugin developer decide to charge $1000 a year for it? This is of course an unlikely scenario, but are there any mechanisms in place to prevent such things?
I have to apologize to Lerg for ranting about there matters here, but I had to let i out somewhere. I actually have one relevant question to you, Lerg.
You write “The plugin will be for sale for $14.99 for a week and $19.99 after that. Subscription based, to make sure I have resources to support it.”
What does this mean? If we pay now, will the plugin cost $14.99 per year for all future? Or the first year?
(*) If you want to maintain your app…
runewinse, it’s ok to express your discontent. I certainly expected that nobody likes when something free becomes paid.
The main goal of the paid marketplace is to attract 3rd party developers that can provide Corona community with useful plugins that otherwise would never be made by Corona Labs itself. It’s better to have a paid plugin than no plugin at all.
$14.99 is for the first week only, so after a year it will be $19.99. Poor wording probably.
I can speak for myself and I can assure you that I won’t increase the price in the future, so nothing ridiculous like $100 or $1000 for a plugin.
Also not all my plugins will become paid, I have basic plugins that don’t require much support as free - flashlight, toast, vibrator. Recently I’ve added Apple’s Taptic Engine support to the vibrator plugin, it took me a few days, but it’s still free.