Re: Will iOS app accepted on App Store if 80% of UI is rendered on UIWebView and 20% being native OCR
> On 20 Aug 2015, at 07:21, Devarshi Kulshreshtha > wrote: > > I have a mobile website which at high level provides these functionalities: > > 1. Sign-in > 2. Sign-up > 3. Few forms where user can fill his additional details > 4. Providing some capabilities to user based on information provided by him > > Now I want to integrate OCR capabilities such as: > > 1. ID card scan > 2. Debit card scan > 3. Void check scan > > So that some of the forms can be automatically filled by information > extracted from these. > > I am planning to make a native app in iOS consuming most of the forms, flow > from my mobile website by rendering respective weburls on webview, and > integrating vendor SDKs to provide OCR capabilities. > > Will Apple accept my iOS app in App Store if I have 80% of flow, UI > rendered on UIWebView and remaining 20% being integration and use of native > vendor SDKs for OCR capabilities? There are many many apps on the store which are basically just a Web View. It would be unlikely for your app to be rejected for that. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Will iOS app accepted on App Store if 80% of UI is rendered on UIWebView and 20% being native OCR
From your description, your app would use official APIs. So in theory, it doesn't matter if your app is just presenting a web view (like a lot of apps). But considering that the interpretation of the App Store Guidelines can vary depending on the reviewer or the weather forecast, the only way to know if your app will be accepted is to submit it to the review process. My $0.02 On Thu, Aug 20, 2015 at 8:21 AM, Devarshi Kulshreshtha wrote: > I have a mobile website which at high level provides these functionalities: > > 1. Sign-in > 2. Sign-up > 3. Few forms where user can fill his additional details > 4. Providing some capabilities to user based on information provided by him > > Now I want to integrate OCR capabilities such as: > > 1. ID card scan > 2. Debit card scan > 3. Void check scan > > So that some of the forms can be automatically filled by information > extracted from these. > > I am planning to make a native app in iOS consuming most of the forms, flow > from my mobile website by rendering respective weburls on webview, and > integrating vendor SDKs to provide OCR capabilities. > > Will Apple accept my iOS app in App Store if I have 80% of flow, UI > rendered on UIWebView and remaining 20% being integration and use of native > vendor SDKs for OCR capabilities? > > > -- > Thanks, > > Devarshi > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/dev.iceberg%40gmail.com > > This email sent to dev.iceb...@gmail.com -- Packaging Resources - http://s.sudre.free.fr/Packaging.html ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash help?
> On 20 Aug 2015, at 07:40, Shane Stanley wrote: > > I'm try to track down a crash, and I'm not sure where to begin. This is what > I see: > > Crashed Thread:0 Dispatch queue: com.apple.main-thread > > Exception Type:EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x07fb9095d6f0 > Exception Note:EXC_CORPSE_NOTIFY > > VM Regions Near 0x7fb9095d6f0: >CoreAnimation 000117933000-000117934000 [4K] rw-/rwx > SM=PRV > --> >STACK GUARD7000-70001000 [4K] ---/rwx > SM=NUL stack guard for thread 5 > > Application Specific Information: > objc_msgSend() selector name: retain > > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libobjc.A.dylib 0x7fff96ee44dd objc_msgSend + 29 > 1 com.apple.CoreFoundation 0x7fff927b8b59 > _CFPreferencesSetValueWithContainer + 153 > 2 com.apple.Foundation 0x7fff91fa30af > -[NSUserDefaults(NSUserDefaults) setObject:forKey:] + 46 > 3 com.apple.CoreFoundation 0x7fff9279ca3f -[NSSet > makeObjectsPerformSelector:] + 223 > 4 com.apple.AppKit 0x7fff8aa5fd26 -[NSIBObjectData > nibInstantiateWithOwner:options:topLevelObjects:] + 1142 > 5 com.apple.AppKit 0x7fff8aa3e9c1 loadNib + 384 > 6 com.apple.AppKit 0x7fff8aa3dee5 > +[NSBundle(NSNibLoading) > _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300 > 7 com.apple.AppKit 0x7fff8abdc7d0 > +[NSBundle(NSNibLoadingInternal) > _loadNibFile:externalNameTable:options:withZone:] + 150 > 8 com.apple.AppKit 0x7fff8abdc588 -[NSWindowController > loadWindow] + 310 > 9 com.apple.AppKit 0x7fff8abd79f3 -[NSWindowController > window] + 80 > 10 com.apple.AppKit 0x7fff8abe8bf2 -[NSWindowController > showWindow:] + 36 > 11 com.apple.AppKit 0x7fff8abfffea -[NSDocument > showWindows] + 93 > 12 com.apple.AppKit 0x7fff8af979dc > __80-[NSDocumentController > openDocumentWithContentsOfURL:display:completionHandler:]_block_invoke1035 + > 200 > 13 com.apple.CoreFoundation 0x7fff927acaec > __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 > 14 com.apple.CoreFoundation 0x7fff9279e865 __CFRunLoopDoBlocks > + 341 > 15 com.apple.CoreFoundation 0x7fff9279e02e __CFRunLoopRun + 910 > 16 com.apple.CoreFoundation 0x7fff9279da38 CFRunLoopRunSpecific > + 296 > 17 com.apple.HIToolbox 0x7fff9a36f3bd > RunCurrentEventLoopInMode + 235 > 18 com.apple.HIToolbox 0x7fff9a36f153 > ReceiveNextEventCommon + 432 > 19 com.apple.HIToolbox 0x7fff9a36ef93 > _BlockUntilNextEventMatchingListInModeWithFilter + 71 > 20 com.apple.AppKit 0x7fff8aac01e7 _DPSNextEvent + 1076 > 21 com.apple.AppKit 0x7fff8ae8c90d -[NSApplication > _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 > 22 com.apple.AppKit 0x7fff8aab60b8 -[NSApplication run] > + 682 > 23 com.apple.AppKit 0x7fff8aa38396 NSApplicationMain + > 1176 > 24 libdyld.dylib 0x7fff89e345ad start + 1 > > It's a document-based app and I can produce it at will by: closing a > document, waiting a couple fo seconds, then opening it (or any other > document). You can repro? That’s a great start! Considering it’s a crash in objc_msgSend, my first suspicion is a zombie. Try running your app with zombies enabled, or using Instruments’ zombie tool and see if that narrows it down at all. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash help?
On 20 Aug 2015, at 7:16 pm, Mike Abdullah wrote: > > Try running your app with zombies enabled I spent a couple of hours playing with that the other day. After your email I tried again: success in minutes, thank you! I was failing to remove an observer... -- Shane Stanley ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Swift: 'If' statement needing parentheses on closure return value property access?
> On 19 Aug 2015, at 07:42, Quincey Morris
> wrote:
>
> Clearly it’s a “more ambiguous” context than the while case, which prevents
> the compiler from realizing that there is an alternative analysis that works.
> In that case, it’s the error message that’s at fault, since it doesn’t really
> tell you what’s wrong. In fact, this “consecutive statements” error almost
> never gives any help, but I guess the compiler is reluctant just to admit it
> has no clue.
>
> On Aug 18, 2015, at 23:04 , Antonio Nunes wrote:
>
>>if (reminder.exclusions.filter { $0.spansTime(t) }.count > 0)
>> {
>
> It might be clearer to write:
>
>> if reminder.exclusions.filter ({ $0.spansTime(t) }).count > 0 {
>
Thanks Quincy that’s what I went with. Now to write up a bug report explaining
the issue and hoping for at least a better error message… :-)
Cheers,
-António
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: Will iOS app accepted on App Store if 80% of UI is rendered on UIWebView and 20% being native OCR
> On Aug 19, 2015, at 11:21 PM, Devarshi Kulshreshtha > wrote: > > Will Apple accept my iOS app in App Store if I have 80% of flow, UI > rendered on UIWebView and remaining 20% being integration and use of native > vendor SDKs for OCR capabilities? Sure, why not? There are many iOS apps built with tools like PhoneGap/Cordova that are 100% run by a UIWebView. What rules do you think Apple has that would cause trouble for this app? —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Private Methods
> On Aug 20, 2015, at 4:10 AM, Jeremy Pereira > wrote: > >> The (Obj-C) compiler knows if a superclass declares a method with the same >> selector. > > Only if the method is declared in in @interface that has been imported. It > could have been declared in a private category or class extension or even not > at all. Yes, that’s what I meant. By “declares” I meant “includes in its public interface”. Obviously the method could be declared privately or only appear in the @implementation. I was just rebutting Maxthon’s assertion that the compiler knows “nothing”. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash help?
> On Aug 20, 2015, at 2:16 AM, Mike Abdullah wrote: > > You can repro? That’s a great start! Considering it’s a crash in > objc_msgSend, my first suspicion is a zombie. Yup. A valuable things to know in Obj-C debugging is that: * 99% of the time, a crash in objc_msgsend means that the receiver of a method-call is a dealloced object. (Enabling Zombies will help track it down.) * The other 1% of the time, it’s a live object that’s been overwritten by a buffer overflow or random heap corruption. (Guard Malloc or, in Xcode 7, the Address Sanitizer, can help.) —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
NSSearchField and Dates
Hello folks, This question is a bit simplistic, but I’m not having luck finding an explanation. This is my first time using NSSearchFields. I’m in the process of binding them to an NSArrayController of data from a previous developer. So far, so good for the most part. However, one of the values to query is an NSDate with the key of “Start Date” (there is a corresponding “End Date” value). How do NSSearchFields interact with NSDate values? What would be the appropriate way to handle this? If I write a dateformatter and add it to the ValueTransformer, does the search field query against that? thanks for any info, Jaime ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash help?
Assert the validity of all your method parameters. While it can help to
assert return results thats less helpful as most return results are later
used as input parameters:
#import
- (void) foo( int *p, int n )
{
assert( NULL != p && n > 0 && n < 10 );
...
return;
}
This might not have found the crash we're discussing but it will find many
others by the time you ship. Also assertions are more effective than
comments for documenting APIs because one is forced to maintain them along
with the rest of the code.
- Mike
--
Michael David Crawford P.E., Consulting Process Architect
mdcrawf...@gmail.com
http://mike.soggywizard.com/
One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To
Light.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Using alarm(3) on background NSOperationQueue threads
From within a background NSOperationQueue thread, the effects of alarm(3) seem to be ignored. (I use alarm() to interrupt certain system calls like connect() when they stall.) The alarm fires, the alarm handler is invoked, but the ongoing sys call is not interrupted, as it would be normally. Is there something inherent in NSOperationQueue that would block the delivery of alarms? Is there another way to effect this? -Carl ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Using alarm(3) on background NSOperationQueue threads
On Aug 20, 2015, at 7:29 PM, Carl Hoefs wrote: > > From within a background NSOperationQueue thread, the effects of alarm(3) > seem to be ignored. (I use alarm() to interrupt certain system calls like > connect() when they stall.) The alarm fires, the alarm handler is invoked, > but the ongoing sys call is not interrupted, as it would be normally. Is > there something inherent in NSOperationQueue that would block the delivery of > alarms? Is there another way to effect this? You can't do this safely. alarm() was effectively obsoleted as soon as multiple threads were introduced. alarm() causes a signal to be delivered to the process, not necessary the calling thread. It may interrupt some system call, but not necessarily the one you want it to. Also, attempts to use alarm() from multiple threads will supersede each other. You should set your sockets to be non-blocking, initiate the connect() which should return -1 and set errno to EINPROGRESS, and then use a file-descriptor-readiness-testing API to determine when the attempt has either succeeded or failed. One approach is to use kqueue with an appropriate time out on the kevent() call. That is a blocking approach. Another approach is to use dispatch sources. You'd create one for the socket and another for a timer. Whichever fires first tells you what happened and you should cancel the other. This is non-blocking. The thread can do other things or be returned to the pool and maybe exit and, when the relevant event occurs, a task will be queued to a queue. If you want to stop a connect attempt that was initiated this way due to the timeout expiring, close() the socket. Regards, Ken ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
