ios - Using in-app purchases for glances and complications in WatchKit -

-

i making native apple watch app, , wondering if can have glances , complications available users have paid in-app purchase.

also, if have not upgraded in-app purchase, when go glance, or click on (disabled) complication, view show saying: "please upgrade pro complications , glances". , there button saying "go app", open app on phone, in-app purchase button be.

is possible?

from developer's perspective:

is possible developer? yes. in regard complication controller, return timeline entries based on existence of valid receipt.

since storekit isn't available on watch, phone have had validate receipts, provide details watch.

you need handle edge cases, such when in-app purchase state indeterminate complication controller (since launches in background before watch app has been launched first time).

complication controllers aren't designed asynchronously fetch (from phone or network). it's expected data on hand, , return results data source requests.

it's not practical have complication controller try fetch (receipt validation) data. @ best, can request data 1 update, manually update complication second time after watch extension knows offer pro data in future.

a more modular approach apple recommends separate functionality session manager provides data data manager, , complication controller retrieves data data manager.

but should following question answered apple, before spend time designing watch app conditional features.

will apple approve it?

what you're proposing show placeholder information on glance or complication.

while there apps on store provide in-app purchases additional complications, apps support @ least 1 complication start.

would app make through review process, since provides no complication (data) start.

that's off-topic question no 1 here able with.

a simple answer "also" feature:

there's no way open ios app (in foreground) watch app. user have open phone app on own, navigate controller offers in-app purchase.


Comments

Post a Comment

Popular posts from this blog

ios - RestKit 0.20 — CoreData: error: Failed to call designated initializer on NSManagedObject class (again) -

-
this error has shown on many times, seems. prominent answer issue seems restkit 0.20 — coredata: error: failed call designated initializer on nsmanagedobject class however, solution posted doesn't work me. let's start beginning: i want upload file server. want parse response make sure uploaded. if not, try again later. model has boolean variable called nsnumber *senttoserver purpose (in coredata, bool saved nsnumber ) . because don't know whether sending going successful, save entity coredata model first before sending via restkit. when post request successful, server returns json string this: {"id":14,"created":true} notice that, of course, id not set on coredata model yet, both id , created new informations model. here's model: @interface recording : nsmanagedobject @property (nonatomic, retain) nsstring * audiofilepath; @property (nonatomic, retain) nsdate * createdat; @property (nonatomic, retain) nsstring * deviceid; @
Read more

java - Digest auth with Spring Security using javaconfig -

-
so i'm trying create digest authentication spring following documentation trying translate xml "requirements" in java requirements. let's have xml in docs: <bean id="digestfilter" class= "org.springframework.security.web.authentication.www.digestauthenticationfilter"> <property name="userdetailsservice" ref="jdbcdaoimpl"/> <property name="authenticationentrypoint" ref="digestentrypoint"/> <property name="usercache" ref="usercache"/> </bean> <bean id="digestentrypoint" class= "org.springframework.security.web.authentication.www.digestauthenticationentrypoint"> <property name="realmname" value="contacts realm via digest authentication"/> <property name="key" value="acegi"/> <property name="noncevalidityseconds" value="10"/> </b
Read more

laravel - PDOException in Connector.php line 55: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) -

-
my .env: app_env=local app_debug=true app_key=myappkey app_url=http://localhost db_connection=mysql db_host=localhost db_port=3306 db_database=gestiontaller db_username=root db_password='root' cache_driver=file session_driver=file queue_driver=sync redis_host=127.0.0.1 redis_password=null redis_port=6379 mail_driver=smtp mail_host=mailtrap.io mail_port=2525 mail_username=null mail_password=null mail_encryption=null i've tried password ", ' , without, restarting server every time. i've tried changing localhost 172.0.0.1. yes, password correct, running mysql -u root -p introducing password root in prompt can go mysql. users table: +------------------+-----------+ | user | host | +------------------+-----------+ | debian-sys-maint | localhost | | mysql.sys | localhost | | root | localhost | | root1 | localhost | +------------------+-----------+ i've added homestead.yaml this: database_port: 3306
Read more