今日已更新 163 条资讯 | 累计 40937 条内容
关于我们

标签:#an

找到 3018 篇相关文章

AI 资讯

What Happens If You Fail Google Play 14 Day Testing Requirement?

When you are aiming to publish an app on the Google Play Store with a personal developer account created on or after November 13, 2023, you must meet closed testing criteria before applying for production access. In December 2024, Google adjusted this requirement from 20 testers down to 12 testers opted in for 14 consecutive days. But what actually happens if you fail google play 14 day testing requirement? Many developers worry that failing will permanently damage their developer standing, trigger account suspensions, or permanently lock their app in testing mode. The reality is more straightforward, though still frustrating if you are eager to launch. Failing to satisfy the requirement manifests in two main ways: an interrupted streak timer that resets before you can submit your request, or an outright rejection from Google when you request production access after completing the 14 days. The Difference Between a Counter Reset and Production Rejection It is essential to understand that failing the testing process can happen at two distinct stages. The first stage is during the active testing window itself. To satisfy Google's criteria, at least 12 testers must remain opted into your closed test every single day for 14 consecutive days. If your opted-in tester count drops below 12 because users opt out or uninstall the app, the 14-day counter pauses or resets. You cannot click the button to apply for production access until that continuous 14-day mark is reached with at least 12 enrolled testers. The second stage occurs after you complete the 14 days and submit your application for production access. At this point, reviewers or automated evaluation scripts at Google analyze the telemetry gathered during those two weeks. If Google determines that your testers were inactive, fake, or unengaged, your application for production will be denied. Why Google Rejects Production Access Applications Reaching 14 days with 12 opted-in accounts in your Play Console dashboard is o

2026-09-09 原文 →
AI 资讯

Nintendo isn’t scared of GTA VI

There's never really been a game like Grand Theft Auto VI before, one that has completely altered the lineup of games around it. Everyone, it seems, is scared of going up against Grand Theft Auto VI. Everyone, that is, except for Nintendo. The company held a 30-minute showcase this morning focused entirely on its Legend […]

2026-09-09 原文 →
AI 资讯

Building an Interactive Excel Dashboard for E-commerce Product Analysis: A Case Study of Jumia Products.

Introduction In this project, I set out to analyze a dataset of products listed on Jumia, one of Africa's leading e-commerce platforms, with the goal of understanding how pricing strategies, discounts, and customer reviews influence overall product performance. Using Microsoft Excel, I cleaned and prepared the raw dataset, engineered new features to categorize products, ran correlation and trend analyses to uncover relationships in the data, and ultimately built an interactive dashboard to present the findings in a clear, business friendly format. The objective was not just to explore the numbers, but to answer practical business questions: Do bigger discounts actually drive more customer engagement? Does price influence how a product is rated? Which products are genuinely performing well, and which ones might need a different pricing or marketing approach? This article breaks down the full process behind how I turned raw data into a finished report from initial data cleaning to the creation of an interactive dashboard. The following is the uncleaned data(original dataset) Data Set Overview. The dataset contains information about products listed on Jumia with the following columns: • Product: Name of the product. • Current Price: The current selling price of the product (in KSh). • Old Price: The original price before discount (in KSh). • Discount: The percentage discount offered on the product. • Review: The number of customer reviews received by the product. • Rating: The average customer rating of the product (out of 5). Data Cleaning and Preparation On a separate sheet after copy pasting the original data set I had to ensure there was no any present duplicate in the dataset. Now that I had removed any duplicates that was present, next process was changing the cell format for each column from General to the appropriate data type i.e. Text for product names, Currency for prices, Percentage for Discount and Number for ratings and reviews. Next, I used Find and Repl

2026-09-08 原文 →
AI 资讯

Presentation: Platform Engineering in the Age of AI

The panelists explain how platform teams adapt to support AI-assisted engineering, highlighting which capabilities belong in the platform. They discuss trade-offs between standardization and developer autonomy, while sharing strategies to manage AI tooling, security guardrails, and shifting workflows. By Stéphane Di Cesare, Davide de Paolis, Stephen Cihak, Camila Macedo, Renato Losio

2026-09-08 原文 →
AI 资讯

Notes on the Pitfalls of iOS Sandbox Accounts and Apple Pay

Introduction Why am I writing this article? The reason is simple: a while ago, a new project at my company required us to integrate Google Pay and Apple Pay. The service had already completed its credit card payment flow. However, management later requested support for Google Pay and Apple Pay as well. Since none of our previous company projects had integrated Apple Pay, I became the first person in the company to take on this task. With the help of AI, the payment integration itself was completed in about one day. However, a new problem came up: The code was finished, but how were we supposed to test it in the UAT environment? This is basically a record of my experience and the problems I encountered while testing Apple Pay in the Sandbox environment. I hope it helps other engineers who are stuck in a similar testing environment. Problem 1: How to Configure the CER and Private Key At the moment, I only have a .p12 file. The payment integration side has already configured the Apple Pay certificate and generated the corresponding CSR. The only remaining step is to configure the environment variables on the application side. The contents of a .p12 file are generally as follows: .p12 ├── Certificate ├── Private Key └── Certificate Chain (may be included) The overall process is: .p12 ├── Extract the Certificate / PEM ├── Extract the Private Key └── Verify that the CSR, Certificate, and Private Key belong to the same key pair The following process uses OpenSSL: # Inspect the p12 contents without outputting the private key openssl pkcs12 -info -in apple-pay.p12 -noout # Extract the certificate openssl pkcs12 \ -in apple-pay.p12 \ -clcerts \ -nokeys \ | openssl x509 -out cert.pem # Extract the private key openssl pkcs12 \ -in apple-pay.p12 \ -nocerts \ -nodes \ | openssl pkey -out private-key.pem -nodes means that the exported private key will not be encrypted again. Therefore, the generated private-key.pem must be stored securely. It should never be committed to Git or pr

2026-09-08 原文 →
开发者

This founder is making cheaper, cleaner steel

The steel industry isn’t exactly known for innovation. Very little has changed about purifying iron ore since the process was invented and commercialized in the 1850s. The majority of steelmakers melt solid iron ore at dizzyingly high temperatures inside blast furnaces, where the material reacts with gases to trigger chemical reactions that remove oxygen. It…

2026-09-08 原文 →
开发者

This geneticist’s age-reversal tech could help restore sight

Yuancheng (Ryan) Lu is obsessed with aging. And with eyes. As he steps outside the Whitehead Institute in Cambridge, Massachusetts, his aviator glasses darken automatically in the sun. Age-related blindness runs in his family. A great-aunt in China, the story goes, was killed crossing a road because she couldn’t see oncoming traffic. And Lu’s own…

2026-09-08 原文 →
AI 资讯

Your Solana Wallet Is Holding Money You Forgot About — Here's the On-Chain Reason Why

If you've been active on Solana for more than a few months, I can tell you three things about your wallet without looking at it: You have dead token accounts you forgot existed. If you've ever traded on pump.fun, there's probably an unclaimed reward sitting in a program you never interacted with. Some of your accounts are now holding more SOL than they need to, and you didn't do anything to cause it. None of this is a bug. It's a side effect of how Solana's storage model works — and once you understand the mechanism, it's actually a pretty elegant piece of design that most people just never get exposed to. Let's go through it. 1. Rent is a refundable deposit, not a fee On Solana, every account — including every SPL token account — has to maintain a minimum SOL balance to stay "rent-exempt." This isn't a subscription. It's a bond: SOL locked against the account's existence, refunded in full the moment you close it. const rentExemptReserve = await connection . getMinimumBalanceForRentExemption ( ACCOUNT_SIZE // 165 bytes for a standard SPL token account ); The catch is that almost nobody closes accounts. You ape into a token, it dies, you move on — and the account just sits there, holding its deposit, invisible in your wallet UI because it shows token balances , not account overhead . Multiply that by every token you've ever touched, every NFT mint you tested, every airdrop you claimed once and ignored, and you're looking at real, non-trivial SOL parked across dozens of accounts doing nothing. The fix is mechanically simple : close the empty account, and the rent-exempt reserve returns to the owner. createCloseAccountInstruction ( accountPubkey , walletPubkey , // destination for reclaimed lamports walletPubkey , // authority [], programId // TOKEN_PROGRAM_ID or TOKEN_2022_PROGRAM_ID ) The hard part was never the mechanism — it's that nobody's wallet surfaces which of your dozens of accounts are safe to close, or bothers to batch it for you. 2. Rent reduction created

2026-09-08 原文 →
AI 资讯

Presentation: A Solopreneur's Journey: From Engineer to Puzzle Master and Storyteller

Joe Cassavaugh shares his journey from software engineer to successful solopreneur with a $2M+ indie franchise. He explains how he scaled production to 10 games in 5 years, adopted Unity to boost velocity 4-6x, optimized content pipelines, and leveraged refactoring patterns. He discusses key trade-offs between corporate engineering and solopreneurship for senior devs and leaders. By Joe Cassavaugh

2026-09-08 原文 →