Cracked vkontakte hacker v1.0 adobe

Ecwid is a service for creating online stores. It offers site builder functionality and integration with a huge number of third-party platforms. With Ecwid, you can create a store on any site or sell products on Instagram in a few clicks, without leaving the social network.
We studied the features of the service and prepared a detailed review of its tools for sales management.

The target audience

Ecwidis a service for doing business. But, despite the commercial focus, he has a workable free tariff. Yes, you can add only 10 products on it, but the basic sales management tools are available. This means that Ecwid can be used even with a minimal budget.
The service offers three approaches to creating an online store. The first is the use of the Start site on Ecwid. Second - add to the directory on a separate site, developed on the other the CMS, the designer of sites or framework. The third is the launch of a full-fledged store inside popular social networks. Due to such a wide range of usage scenarios, the service has the widest possible audience.
Ecwid's popularity has also been influenced by simplicity. An independent site is assembled from ready-made blocks and configured in visual mode, adding a directory to a third-party resource is performed by inserting a code or widget, the store on social networks is launched in a few clicks. At the same time, the service remains flexible enough to support the work of very large projects - the quantity of goods is unlimited at an unlimited tariff.
All these characteristics make Ecwid a universal tool for creating online stores, which can be useful for both small businesses and large retailers.

Functionality

Ecwid offers immediate coverage of all possible sales channels. You create one showcase that can be used as a separate site, placed on the page of other portals, sent to social networks or distributed through your own mobile application. Everywhere store functionality remains:

• Product cards with photos, descriptions, prices, equipment options.
• Cart for placing an order.
• Online payment for goods.
• The choice of delivery method.
• Reliable protection of personal data of customers, including payment information.

After registering with Ecwid, you get the Start site for free. This is a one-page with an integrated store. To start sales, you only need to replace photos and descriptions, if desired, change the design. The list of required steps is in the setup wizard, which opens when you first enter the control panel. The minimum set of actions is as follows:

1. Create an account.
2. Store launch.
3. Adding products. There are examples in the catalog, you can delete or edit them.
4. Check geographic settings. In addition to the country, you must select the currency and unit of weight.
5. Configure delivery methods.
6. Set up payment methods.

You can do without the setup wizard. The control panel is fully translated into Russian and offers a very simple structure.

• Section "Store Management". Includes tools for managing sales, catalogs and promotions. There is also a tab with reports on the work of the store.
• The “Sales channels” section offers to set up different distribution options for goods: through other sites, social networks, marketplaces.
• The “Configuration” section contains design, payment, delivery settings, as well as a link to the application store to expand the basic functionality of the service.

After setting up the start site, you yourself choose which other sales channels to use. Can:

1. Launch a store on social networks: Instagram, Facebook, VKontakte.
2. Unload goods on popular trading platforms: Yandex.Market, Google Shopping, eBay.
3. Place the product widget on the page of any site or add a storefront as a separate page.
4. Use the mobile app store.

Orders from all channels are collected in a single Eswid admin panel. From here you can process and execute them, and then update the catalog taking into account the remaining goods. Changes will be synchronized on all distribution channels.
In addition to selling physical goods and services, Ecwid offers to organize the distribution of digital goods: electronic music, books, photos, videos. Ecwid provides hosting, so there is no need to look for other sites for storing files. File size depends on the tariff plan. A maximum of 10 GB is available per file.
To create a digital product when creating a card, you must download the corresponding file. Buyers will have access to it through a special link that is sent to the mail after successful payment. There are two ways to protect a digital product link from distribution and reuse:

1. Set expiration date. The buyer can use the link only during the specified time.
2. Limit the number of product downloads on one link.

The methods can be used simultaneously. For example, to limit the time for downloading to 48 hours and to limit the number of downloads 3. There is also the opportunity to distribute free promotional items - just set the price to zero and remove the restrictions on the number of downloads.
Since digital goods do not require delivery, this order parameter must be disabled. In the control panel, this can be done through the "Taxes and Delivery" tab, in the mobile application - in the "Delivery" section.

Payment and delivery of goods

Ecwid supports several methods of making payments for goods:

• Bankcard. To implement this method, you must connect one of the available payment systems to the store. In total, there are about 50 items in the list of supported services, of which 16 work in Russia: Yandex. Kassa, Robokassa, Sberbank, etc. For connecting each payment system there is detailed instruction in the Ecwid knowledge base.
• Electronic money. For processing, a payment system is also required - for example, Yandex. Kassa or Robokassa, which can work with bank cards and with electronic money.
• Offline payment methods: cash on delivery and cash on delivery. When setting up, you can change the name of the method, add a note or detailed instructions.
• Bank transfer It is added manually in the section with offline payment methods. When editing, you write where to send the money, or tell how the client will receive your details.

After setting payment methods, you must select the delivery options. Ecwid allows you to create geographic areas with different ways of sending goods. For example, if the product is physically located in Moscow, then the residents of this city have the opportunity to pick it up on their own. Pickup is not suitable for buyers from other regions, so it makes no sense to show it among the delivery methods. You can also prohibit delivery to specific areas. When you try to place an order for an address from an inaccessible territory, the buyer will see a notification that this is not possible.
There are four strategies available when calculating shipping costs:

1. Automatic calculation - the tariff is calculated by the company that will deliver the goods.
2. Individual calculation - setting your own tariffs based on the weight of the goods or the value of the order.
3. Fixed rate - you can choose the average value and set it for all products.
4. Free shipping. The most common way is free shipping when making a purchase for an amount higher than a certain amount.

Delivery settings are detailed in the Ecwid knowledge base. The instructions help you choose the right options and set fair rates.

Mobile management application

Already at a lower paid tariff, store owners can use the application for Android and iOS, through which they can perform basic operations for managing the site:

1. Add products along with photos, descriptions and prices.
2. Track stocks using the barcode scan feature.
3. Receive notifications of new purchases.
4. Process orders: change status, contact customer, accept payment.
5. Advertise products and talk about new promotions through social networks using the "Share" function.
6. Create discount coupons and manage bonus programs.

You can try the mobile application for free for 14 days. To get unlimited access to its use, you must purchase one of Ecwid's paid tariffs.

Mobile Shopping App

With an annual subscription to the Unlimited tariff, you can order the development of a store application for Android and iOS. The service team will set up synchronization with your store and publish the application in the Apple App Store and Google Play.
In the mobile application, the same features are available as on the store’s website. The client can browse the catalog, add products to the basket, pay for the order. The application is synchronized with the main site. Any changes you make to the control panel are instantly displayed on the site and in the application.

Compliance 54-FZ

Since 2017, amendments to the law "On the use of cash registers" have been in force in Russia, according to which entrepreneurs are required to send an electronic check to the tax authorities after each sale. The requirement also applies to the operation of online stores, therefore, when choosing tools for their creation, it is necessary to clarify the availability of this opportunity.
Ecwid provides solutions for online and offline stores. The service itself does not store, does not process customer data and does not transfer money. He only acts as an intermediary between the buyer and the payment system. Therefore, compliance with 54-ФЗ depends on the payment method chosen. Ecwid offers several methods that support the required format of fiscal documents (FFD 1.05).

1. For an online store: Yandex.Cash, Robokassa, Sberbank, Tinkoff Payment, CloudKassir, PayAnyWay, NextPay, ArsenalPay.
2. For an offline store: issuing a bank account, POS-system, mobile terminals, cash desk on a smartphone using the Cashier MySklad application, as well as a new cash desk.

If standard solutions are not suitable, you can develop an individual method for transferring data to the tax or order it from the Ecwid team.

Integration with other sites

Ecwid is great for launching full-fledged online stores on other platforms. With it, you can implement sales on any website or social network:

• CMS Wordpress , Joomla and others.
• Website builders uKit , Wix , Weebly , Squarespace, Adobe Muse , Tilda and others.
• Social networks “VKontakte”, Instagram, Facebook, Tumblr, Blogger.

To add Ecwid functionality to the site, just insert the integration codes. If there are few goods, you can use the widget. Integration with third-party platforms is already available at a free Ecwid tariff. The only exception is that without payment you will not be able to use the service to work with the store on Facebook.
The main integration option is automatic unloading of the product catalog and adding functionality to pay for the order. For example, you can create a store on a separate site, and then transfer the entire assortment to a group in VKontakte in a few clicks. Data is synchronized: all changes on the site will be instantly displayed in the community directory.
If you have a store on Facebook and shopping tags are active, then its catalog can be used to sell products on Instagram. To do this, you need a business account. Thanks to him, you can mark products in posts. The subscriber touches the photo to see the name and cost of the indicated positions. When clicked, he goes to a separate page with other pictures and a detailed description of the product. It also displays another marked assortment and similar posts from the store.
After adding 9 posts with goods in the profile, the link “To the store” appears. When you click on it, the buyer gets to the page with all the marked products. He can see the available photos, read the description, see the prices and, most importantly, make a purchase without leaving the social network. Such ease of order increases conversion. Given the growth of Instagram audience and the general development of the social network in the direction of sales, the launch of such a functional store is an excellent opportunity to increase business profits.

Ecwid App Store

To expand the basic functionality on Ecwid there is a built-in application store. It presents free and paid solutions for marketing, window dressing, analytics, website optimization and promotion. For example, you can add a widget that shows a random product, a block with smart recommendations, a currency converter.
To get the application, just go to its page in the Store and click "Install." Free extensions are installed immediately, some paid ones have test periods. You can manage plugins on the "My Applications" tab in the admin panel.

Designs and work with templates

The design tab is responsible for the appearance of the display case. It provides a step-by-step list of settings for the store interface. You only need to choose the appropriate options.

1. Image size: large, medium, small.
2. The format of the photos is 1: 1, 4: 3, 3: 2, 2: 3, 3: 4. It also includes dimming the background of images. This is useful if the color of the photo merges with the background of the page, and you want to visually highlight the pictures.
3. Product information: centering, adding a frame around the image, setting up the show or hide the name, price, article, Buy button, additional photos.
4. Category name - select a location relative to the photo or hide the title.
5. Product page view - the number of columns and the location of the description relative to the photo.
6. Gallery view on the product page - horizontal or vertical arrangement of thumbnails, display of full-size images.
7. Information displayed on the product page: name, navigation chain, article number, price, a field in the “Stock”, the quantity of goods available, the quantity of goods when ordering, wholesale cost, description, buttons “Share”.

There is a separate block with settings for the directory. Here, the Login button is added and removed to authorize customers, the menu at the bottom of the page, the navigation chain, the Sort field, which allows customers to choose a convenient order for displaying goods: by price, by name, etc. A convenient function when inserting a directory on a page of a separate site is the auto-detection of color. The background of the window will adjust itself to the color scheme of the page.
To adjust the appearance of the Start site, a different editing mode is used. To go to it, open the store user interface. The “Edit” button will be on top. In this mode you can:

1. Choose a theme for your site.
2. Change the title and description, add your cover.
3. Rewrite texts in all auxiliary units: customer reviews, store information, history, contacts, etc.
4. Swap blocks or disable extra sections.

You cannot add sections yourself - you use only those blocks that are initially available in the selected topic. You can purchase a professional template or install add-ons for design in the application store. Plugins add a style editor that allows you to change the font, appearance of buttons, input forms, drop-down lists. There is also a layout editor that expands the variability of the placement of goods and their descriptions on the page.
It is possible to create your own CSS theme. You can change individual elements or completely redo the design of the display case. The editor allows you to add an unlimited number of CSS themes, but only one can be used for styling.

Optimization (SEO) and promotion

Ecwid is optimized by default for search engine requirements. However, this does not mean that you do not have to do anything. In order for the site to appear on the first page of search results for relevant queries, in addition to optimization, promotion is also needed.
First, let's see what Ecwid has for SEO.

1. Automatically create and update site maps. Thanks to it, search robots quickly find and index products, adding them to search results.
2. Micro-layout Schema.org on all pages of the store. It allows the search engine to navigate the array of information, determine the categories and names of goods, as well as other useful data.
3. Automatic generation of static copies of pages for transmission to search engines. This solves the dynamic content indexing problem inherent in the JavaScript services to which Ecwid belongs.
4. The formation of readable links that both search engines and users alike. On most platforms, they work by default. On Joomla, Adobe Muse, and some other sites, clean links are manually configured - instructions are in the Ecwid knowledge base.
5. Adding ALT descriptions to all images. By default, the name of the product is registered in them.
6. Configure robots.txt to tell the search engine which pages should be indexed and which should not. There is also a simple switch to completely ban or allow site indexing.

Meta tags of the store’s main page are automatically generated from the title and description. Therefore, they need to indicate what you want to see in the search results.
Meta tags for pages with categories and products are formed from the title and description. On paid tariffs, you can change them manually.

1. Switch to the Ecwid control panel.
2. Go to the “Catalog” - “Products” or “Categories”.
3. Open the product or category page.
4. Select the SEO tab.
5. Manually write the page title and description. This data will be used in meta tags.

The website is being promoted on Ecwid by standard methods for stores: keywords in the name and description of the product, customer reviews, and ratings. To attract an audience from social networks in the control panel there are "Share" buttons. They can be added to the storefront so that customers can also share links to their favorite products:

1. Open the Design section in the control panel.
2. In the "Information on the page" section, check the "Share" buttons.

To analyze user behavior and collect statistics, Ecwid suggests using popular services - Google Analytics and Yandex.Metrica.

Price policy

Ecwid has a free fare on which you can place up to 10 products. The number of sales channels is not limited. The tariff offers responsive design, integration with all available platforms except the Facebook Store. Technical support in this case is carried out only by mail.
There are three paid tariffs:

1. Venture (950 rubles/month**)** - up to 100 products, Facebook Store, an application for managing the store for Android and iOS, advanced SEO, bonus programs, support by mail and chat.
2. Business (2275 rub/month**)** - up to 2500 products, the ability to unload goods to trading floors, tracking abandoned baskets with automatic sending of reminders to customers, wholesale prices, advanced filtering tools, mail, chat, and phone support, 2 hours for developing atypical decisions.
3. Unlimited (5250 rubles/month**)** - without restrictions on the number of products, all available designer features, including a mobile application for buyers on Android and iOS when paying a yearly subscription. 12 hours to develop non-standard solutions.

It is more profitable to pay immediately for the year of using the service - the savings are about 20%. There are no hidden fees, no sales commission. You pay the cost indicated in the description of the tariff plan and get a full list of services. You can change the tariff or unsubscribe at any time, however, money for unused services is not returned.

Advantages and disadvantages

The main advantage of the service is openness. While many designers are creating a closed ecosystem, prohibiting the transfer of sites to other sites and complicating the export of goods, Ecwid offers the simplest integration with a variety of platforms. Among other advantages, we highlight:

• A free tariff plan that can be used in practice, albeit with a limit of up to 10 products.
• Automatic creation of the Start site when registering at Ecwid.
• Convenient integration with other sites. Ecwid showcase can be inserted on any page, and goods can be easily uploaded to social networks.
• A single control panel that receives information from all channels of distribution of goods: through its own website, other web pages, marketplaces, social networks.
• Access to the main control panel tools through the mobile application.
• The ability to sell digital goods.
• Tools for promoting and attracting customers: discount and bonus programs, return of abandoned baskets, wholesale prices, advanced retargeting settings.
• Support for various payment and delivery methods.
• Built-in reports and analytics, as well as a simple connection of Yandex.Metrica and Google Analytics.
• Responsive design and simple window dressing tools.
• Own mobile application for buyers.
• An open API for those who want to radically redesign the store’s design or create an application for it.

Among the shortcomings, we note a weak block with SEO settings. For example, you cannot register product URLs. By default, the product name is used. Such a link looks harmonious and attractive, but the inability to change the address is still frustrating - I would like a little more flexibility, and now even extensions from the application store do not help.
Another pedestal towards Ecwid is the lack of support for accelerated AMP loading on product pages. If the user has a slow Internet connection, then there may be problems with the display of cards - they will be loaded for a very long time.

Conclusions and recommendations

When registering, Ecwid gives you a Start site that you can use to sell products after a short setup. Replace images and texts, edit product cards, add current payment and delivery methods - the store is ready. Yes, it is very small, but everything works: the buyer comes in, looks at the catalog, selects goods, places an order, indicates the appropriate delivery method. Total - a full sales cycle in just a couple of hours after registering for the service.
One of the main advantages of Ecwid is a large number of application scenarios. You can use different sales channels: sites, social networks, marketplaces like Yandex.Market or Amazon. For example, you can agree with the owners of other sites to place a widget with individual products or a showcase with a full catalog. With this placement, all the necessary functionality is preserved. The user will be able to see photos of the goods, read the description, see the cost and proceed to payment, as if he was on your site.
Ecwid generally offers the most simple and convenient integration with third-party sites. You have a good audience on VKontakte - upload goods to the community in one click and get new orders. We started from the store on Instagram - add posts for sale, so that subscribers place orders without leaving the social network. Sales from all channels will be displayed in a single admin panel, including through the mobile application. Is it possible to come up with a simpler management system for essentially several stores, albeit with the same interface? I think no. Ecwid sets the standard for convenience, after which it will be difficult for you to get used to the fact that other designers are locked in on themselves.

=== application info ===
Version: 1.0.8 (108) Package: de.schildbach.wallet.speedcoins Test/Prod: prod Time: 2018-02-20 21:22:13 +0200 Time of launch: 2018-02-20 21:22:01 +0200 Time of last update: 2018-02-20 21:13:15 +0200 Time of first install: 2018-02-20 21:13:15 +0200 Network: org.speedcoin.production Keychain size: 1 Transactions: 0 Inputs: 0 Outputs: 0 (spent: 0) Last block seen: 804956 (e340991d41f9229fd8033b769ff9505caf81d0b02ef77e5f37ced5df91b1634f) Databases: address_book address_book-journal
Contents of FilesDir /data/use0/de.schildbach.wallet.speedcoins/files: 2018-02-20 21:14:20 4096 files - 2018-02-20 21:13:37 157 key-backup-base58 - 2018-02-20 21:14:20 156 wallet-protobuf - 2018-02-20 21:13:37 157 key-backup-base58.82
Contents of LogDir /data/use0/de.schildbach.wallet.speedcoins/app_log: 2018-02-20 21:13:37 4096 app_log - 2018-02-20 21:22:07 405884 wallet.log
=== stack trace ===
java.lang.NullPointerException: Attempt to invoke virtual method 'android.graphics.drawable.Drawable com.actionbarsherlock.internal.widget.IcsLinearLayout.getBackground()' on a null object reference at com.actionbarsherlock.widget.ActivityChooserView.(ActivityChooserView.java:234) at com.actionbarsherlock.widget.ActivityChooserView.(ActivityChooserView.java:202) at com.actionbarsherlock.widget.ActivityChooserView.(ActivityChooserView.java:192) at com.actionbarsherlock.widget.ShareActionProvider.onCreateActionView(ShareActionProvider.java:164) at com.actionbarsherlock.internal.view.ActionProviderWrapper.onCreateActionView(ActionProviderWrapper.java:23) at android.view.ActionProvider.onCreateActionView(ActionProvider.java:98) at com.android.internal.view.menu.MenuItemImpl.getActionView(MenuItemImpl.java:583) at android.widget.ActionMenuPresenter.getItemView(ActionMenuPresenter.java:237) at android.widget.ActionMenuPresenter.flagActionItems(ActionMenuPresenter.java:663) at com.android.internal.view.menu.MenuBuilder.flagActionItems(MenuBuilder.java:1087) at com.android.internal.view.menu.BaseMenuPresenter.updateMenuView(BaseMenuPresenter.java:87) at android.widget.ActionMenuPresenter.updateMenuView(ActionMenuPresenter.java:441) at com.android.internal.view.menu.MenuBuilder.dispatchPresenterUpdate(MenuBuilder.java:262) at com.android.internal.view.menu.MenuBuilder.onItemsChanged(MenuBuilder.java:981) at com.android.internal.view.menu.MenuBuilder.startDispatchingItemsChanged(MenuBuilder.java:1004) at com.android.internal.policy.PhoneWindow.preparePanel(PhoneWindow.java:650) at com.android.internal.policy.PhoneWindow.doInvalidatePanelMenu(PhoneWindow.java:991) at com.android.internal.policy.PhoneWindow$1.run(PhoneWindow.java:293) at android.os.Handler.handleCallback(Handler.java:815) at android.os.Handler.dispatchMessage(Handler.java:104) at android.os.Looper.loop(Looper.java:207) at android.app.ActivityThread.main(ActivityThread.java:5932) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:955) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:816)
=== device info ===
Device Model: U20 Android Version: 6.0 Board: U20 Brand: Meizu Device: U20 Display: Flyme 6.2.0.0G Finger Print: Meizu/meizu_U20/U20:6.0/MRA58K/1513183743:userelease-keys Host: Mz-Builder-l11 ID: MRA58K Product: meizu_U20 Tags: release-keys Time: 1513184177000 Type: user User: flyme Configuration: {0.94 255mcc1mnc ru_RU ldltr sw360dp w360dp h618dp 480dpi nrml long port finger -keyb/v/h -nav/h s.11} Screen Layout: size 2 long 32 Display Metrics: DisplayMetrics{density=3.0, width=1080, height=1920, scaledDensity=2.82, xdpi=480.0, ydpi=480.0} Memory Class: 256/512
=== installed packages ===
android 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.activate.activatephone 1.0 (1) - 2017-12-13 2017-12-13 com.adobe.reader 18.0.0.181869 (181869) - 2018-01-25 2018-02-10 com.android.alarmclock 6.2.15-2017112815 (6002015) - 2017-12-13 2017-12-13 com.android.backupconfirm 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.bluetooth 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.bluetoothmidiservice 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.browser 6.9.511-2018012510 (6109511) - 2017-12-13 2018-02-15 com.android.calendar 6.8.1-2017112815 (6008001) - 2017-12-13 2017-12-13 com.android.calllogbackup 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.captiveportallogin 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.carrierconfig 1.0.0 (1) - 2017-12-13 2017-12-13 com.android.certinstaller 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.chrome 64.0.3282.137 (328213701) - 2018-01-25 2018-02-01 com.android.defcontainer 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.dialer 3.3.1-2017112815 (3003001) - 2017-12-13 2017-12-13 com.android.email 2.11.1-2017112815 (102011001) - 2017-12-13 2017-12-13 com.android.externalstorage 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.htmlviewer 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.incallui 6.2.3 (623) - 2017-12-13 2017-12-13 com.android.inputdevices 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.keychain 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.location.fused 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.managedprovisioning 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.mms 6.2.6-2017112817 (6002006) - 2017-12-13 2017-12-13 com.android.mms.service 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.musicfx 5.0.0 (50000) - 2017-12-13 2017-12-13 com.android.packageinstaller 6.3.1 (40) - 2017-12-13 2017-12-13 com.android.pacprocessor 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.phone 6.1.3 (6001003) - 2017-12-13 2017-12-13 com.android.printspooler 1 (1) - 2017-12-13 2017-12-13 com.android.providers.applications 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.providers.calendar 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.providers.contacts 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.providers.downloads 6.5.3 (6005003) - 2017-12-13 2018-01-29 com.android.providers.downloads.ui 6.5.3 (6005003) - 2017-12-13 2018-02-18 com.android.providers.media 6.0.170707 (801) - 2017-12-13 2017-12-13 com.android.providers.settings 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.providers.telephony 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.providers.userdictionary 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.proxyhandler 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.server.telecom 6.2.3 (623) - 2017-12-13 2017-12-13 com.android.settings 6.1.70607 (6000018) - 2017-12-13 2017-12-13 com.android.sharedstoragebackup 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.shell 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.soundrecorder 6.4.0-2017112815 (6004000) - 2017-12-13 2017-12-13 com.android.statementservice 1.0 (1) - 2017-12-13 2017-12-13 com.android.stk 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.systemui 6.1.6 (6001005) - 2017-12-13 2017-12-13 com.android.vending 8.9.24-all [0] [PR] 184891514 (80892400) - 2018-01-25 2018-02-10 com.android.vpndialogs 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.wallpapercropper 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.android.webview Developer Build (1) - 2017-12-13 2017-12-13 com.cootek.smartinputv5.skin.keyboard_theme_meizu_white 6.2.6.0 (9) - 2018-01-25 2018-01-25 com.discord 6.2.4 (624) - 2018-02-20 2018-02-20 com.emoji.keyboard.touchpal 6.5.6.5 (5213) - 2018-01-25 2018-01-25 com.facebook.katana 159.0.0.38.95 (91889149) - 2018-01-25 2018-02-15 com.facebook.orca 153.0.0.17.94 (91829660) - 2018-01-25 2018-02-15 com.flyme.netadmin 6.1.34-2017112815 (6001034) - 2017-12-13 2017-12-13 com.flyme.systemuitools 6.1.6 (6001004) - 2017-12-13 2017-12-13 com.gd.mobicore.pa 3.96 (196704) - 2017-12-13 2017-12-13 com.goodix.fingerprint 1.0.02 (2) - 2017-12-13 2017-12-13 com.google.android.apps.docs 2.18.052.03.45 (180520345) - 2018-01-25 2018-02-17 com.google.android.apps.maps 9.71.0 (971003244) - 2018-01-25 2018-02-15 com.google.android.apps.photos 3.14.0.185628364 (2251866) - 2018-01-25 2018-02-16 com.google.android.apps.plus 9.30.0.185461795 (419562437) - 2018-01-25 2018-02-15 com.google.android.apps.translate 5.16.0.RC09.184610470 (59160962) - 2018-01-25 2018-02-09 com.google.android.feedback 6.0-2324235 (23) - 2018-01-25 2018-01-25 com.google.android.gms 11.9.75 (448-182402865) (11975448) - 2018-01-25 2018-01-27 com.google.android.googlequicksearchbox 7.20.18.21.arm64 (300760629) - 2018-01-25 2018-02-09 com.google.android.gsf 6.0-2324235 (23) - 2018-01-25 2018-01-25 com.google.android.gsf.login 6.0-2324235 (23) - 2018-01-25 2018-01-25 com.google.android.onetimeinitializer 6.0-2324235 (23) - 2018-01-25 2018-01-25 com.google.android.partnersetup 6.0-2324235 (23) - 2018-01-25 2018-01-25 com.google.android.play.games 5.4.39 (178940931.178940931-048) (54390048) - 2018-01-25 2018-01-25 com.google.android.syncadapters.calendar 5.0-1545478 (21) - 2018-01-25 2018-01-25 com.google.android.syncadapters.contacts 6.0-2324235 (23) - 2018-01-25 2018-01-25 com.google.android.youtube 13.05.52 (1305523440) - 2018-01-25 2018-02-15 com.ibimuyu.lockscreen 2.0.101 (101) - 2017-12-13 2017-12-13 com.instagram.android 32.0.0.16.94 (91882539) - 2018-01-25 2018-02-13 com.mediatek 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.atci.service 1.0 (1) - 2017-12-13 2017-12-13 com.mediatek.batterywarning 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.connectivity 1.0 (1) - 2017-12-13 2017-12-13 com.mediatek.engineermode 1.0 (1) - 2017-12-13 2017-12-13 com.mediatek.fwk.plugin 1.0 (1) - 2017-12-13 2017-12-13 com.mediatek.gba 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.ims 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.lbs.em2.ui 1.0 (1) - 2017-12-13 2017-12-13 com.mediatek.mdmlsample 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.mtklogger 4.0.0 (40000) - 2017-12-13 2017-12-13 com.mediatek.providers.drm 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.sensorhub.ui 2.0 (2) - 2017-12-13 2017-12-13 com.mediatek.thermalmanager 1.0 (1) - 2017-12-13 2017-12-13 com.mediatek.wfo.impl 6.0-1513183743 (23) - 2017-12-13 2017-12-13 com.mediatek.ygps 1.1 (2) - 2017-12-13 2017-12-13 com.meizu.account 6.2.9-2017120419 (6002009) - 2017-12-13 2017-12-13 com.meizu.alphame 1.3.9-2017112816 (1003009) - 2017-12-13 2017-12-13 com.meizu.backup 2.1.9-2017112815 (2001009) - 2017-12-13 2017-12-13 com.meizu.battery 6.3.8-2017112816 (6003008) - 2017-12-13 2017-12-13 com.meizu.callsetting 6.2.10-2017112815 (6002010) - 2017-12-13 2017-12-13 com.meizu.cloud 6.3.1 (6003001) - 2017-12-13 2017-12-13 com.meizu.connectivitysettings 6.0.102 (6000102) - 2017-12-13 2017-12-13 com.meizu.customizecenter 6.4.1-2017100919 (6004001) - 2017-12-13 2017-12-13 com.meizu.datamigration 1.5.3-2017120814 (1005003) - 2018-01-25 2018-01-25 com.meizu.dataservice 2.1.5 (27) - 2017-12-13 2018-01-25 com.meizu.documentsui 6.0.2-2017080720 (6000002) - 2017-12-13 2017-12-13 com.meizu.experiencedatasync 2.6.0 (10) - 2017-12-13 2017-12-13 com.meizu.filemanager 6.6.1-2017112815 (6006001) - 2017-12-13 2017-12-13 com.meizu.flyme.android.theme.LRA_Soft 1.0 (1) - 2017-12-13 2017-12-13 com.meizu.flyme.android.theme.LRA_Strong 1.0 (1) - 2017-12-13 2017-12-13 com.meizu.flyme.calculator 6.8.0-2017112815 (6008000) - 2017-12-13 2017-12-13 com.meizu.flyme.childrenlauncher 6.1.12-2017090516 (6001012) - 2017-12-13 2017-12-13 com.meizu.flyme.easylauncher 6.2.9-2017112815 (6002009) - 2017-12-13 2017-12-13 com.meizu.flyme.hometools 6.0.0-2017080719 (6000000) - 2017-12-13 2017-12-13 com.meizu.flyme.input 6.4.91-2017112815 (6004091) - 2017-12-13 2017-12-13 com.meizu.flyme.launcher 6.10.2-2017112816 (6010002) - 2017-12-13 2017-12-13 com.meizu.flyme.service.find 6.1.13-2017112815 (6001013) - 2017-12-13 2017-12-13 com.meizu.flyme.toolbox 6.5.3-2017112816 (6005003) - 2017-12-13 2017-12-13 com.meizu.flyme.update 6.6.1-2017113010 (6006001) - 2017-12-13 2017-12-13 com.meizu.flyme.weather 2.0.5-2017112816 (2900005) - 2017-12-13 2017-12-13 com.meizu.location 1.3.2 (1003002) - 2017-12-13 2017-12-13 com.meizu.media.camera 6.5.37-2017112814 (6005037) - 2017-12-13 2017-12-13 com.meizu.media.gallery 6.3.16-2017112811 (60003016) - 2017-12-13 2017-12-13 com.meizu.media.music 6.7.12-2017112815 (6007012) - 2017-12-13 2017-12-13 com.meizu.media.video 6.9.0-2017112815 (6009000) - 2017-12-13 2017-12-13 com.meizu.mzsimcontacts 2.2.1-2017112815 (2002001) - 2017-12-13 2017-12-13 com.meizu.mzsyncservice 6.4.3-2017112917 (6004003) - 2017-12-13 2017-12-13 com.meizu.net.search 6.6.0-2017112815 (6006000) - 2017-12-13 2017-12-13 com.meizu.notepaper 6.9.13-2017112815 (6009013) - 2017-12-13 2017-12-13 com.meizu.perfui 1.0 (1) - 2017-12-13 2017-12-13 com.meizu.powersave 6.2.14-2017112816 (6002014) - 2017-12-13 2017-12-13 com.meizu.privacy 6.0 (6) - 2017-12-13 2017-12-13 com.meizu.safe 4.5.0-2017112917 (4005000) - 2017-12-13 2017-12-13 com.meizu.setup 6.2.0-2017112817 (6002000) - 2017-12-13 2017-12-13 com.meizu.share 2.0.19-2017120617 (2000019) - 2017-12-13 2017-12-13 com.meizu.splitloccontroller 1.0 (1) - 2017-12-13 2017-12-13 com.meizu.systemwallpaper 6.0.3-2017080719 (6000003) - 2017-12-13 2017-12-13 com.mtk.telephony 1.0 (1) - 2017-12-13 2017-12-13 com.nimses 2.0 (107) - 2018-01-25 2018-02-11 com.pyrsoftware.pokerstars.com 1.94.2 (20949) - 2018-02-05 2018-02-17 com.reddit.frontpage 2.22.9 (203159) - 2018-02-20 2018-02-20 com.shazam.android 8.3.1-180206 (803100) - 2018-01-26 2018-02-13 com.soundcloud.android 2018.02.14-release (921) - 2018-01-26 2018-02-15 com.supercell.clashofclans 9.434.30 (958) - 2018-01-25 2018-02-09 com.svox.pico 1.0 (1) - 2017-12-13 2017-12-13 com.tencent.qqlive.player.meizu 1.6.9 (1006009) - 2018-01-25 2018-01-25 com.via.bypass MTK JB 1.1 (1) - 2017-12-13 2017-12-13 com.viber.voip 8.3.0.13 (220330) - 2018-01-25 2018-02-20 com.vkontakte.android 5.3 (1742) - 2018-01-25 2018-02-17 com.vlife.mxlock.wallpaper 5.171.1 (901) - 2017-12-13 2017-12-13 com.webmoney.my 3.2.1 , build f7652c6c0 (31200032) - 2018-02-05 2018-02-06 com.whatsapp 2.18.46 (452171) - 2018-01-25 2018-02-09 com.xrom.intl.appcenter 4.1.420-2017120415 (400100420) - 2017-12-13 2017-12-13 de.schildbach.wallet.speedcoins 1.0.8 (108) - 2018-02-20 2018-02-20 free.vpn.unblock.proxy.vpnmaster 6.3.1 (2018020114) - 2018-01-28 2018-02-02 ginlemon.flowerfree 3.26.010 (503) - 2018-01-25 2018-02-06 org.telegram.messenger 4.8.4 (12207) - 2018-01-25 2018-02-20 piuk.blockchain.android 6.9.2 (293) - 2018-02-20 2018-02-20 ru.yandex.yandexnavi 2.95 (2951961) - 2018-01-25 2018-02-20 smarty.sale.smartysale 1.2.3 (23) - 2018-01-31 2018-02-06 ua.slando 4.15.13 (853) - 2018-01-26 2018-02-09
=== saved exceptions ===
--- collected at 2018-02-20 21:13:38 +0200 on version 1.0.8 (108) java.lang.RuntimeException: https://speedcoin.org/lib/android/version?current=108 at de.schildbach.wallet.ui.WalletActivity$14.handleException(WalletActivity.java:633) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:101) Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:333) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85) Caused by: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) ... 12 more Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. ... 18 more
Cause:
javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:333) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85) Caused by: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) ... 12 more Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. ... 18 more
Cause:
java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85) Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. ... 18 more
Cause:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85)
--- collected at 2018-02-20 21:22:02 +0200 on version 1.0.8 (108) java.lang.RuntimeException: https://speedcoin.org/lib/android/version?current=108 at de.schildbach.wallet.ui.WalletActivity$14.handleException(WalletActivity.java:633) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:101) Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:333) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85) Caused by: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) ... 12 more Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. ... 18 more
Cause:
javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:333) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85) Caused by: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) ... 12 more Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. ... 18 more
Cause:
java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85) Caused by: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. ... 18 more
Cause:
java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. at com.android.org.conscrypt.TrustManagerImpl.checkTrusted(TrustManagerImpl.java:324) at com.android.org.conscrypt.TrustManagerImpl.checkServerTrusted(TrustManagerImpl.java:225) at com.android.org.conscrypt.Platform.checkServerTrusted(Platform.java:115) at com.android.org.conscrypt.OpenSSLSocketImpl.verifyCertificateChain(OpenSSLSocketImpl.java:571) at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:329) at com.android.okhttp.internal.http.SocketConnector.connectTls(SocketConnector.java:103) at com.android.okhttp.Connection.connect(Connection.java:167) at com.android.okhttp.Connection.connectAndSetOwner(Connection.java:209) at com.android.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:128) at com.android.okhttp.internal.http.HttpEngine.nextConnection(HttpEngine.java:353) at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:342) at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:260) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:454) at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:114) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.connect(DelegatingHttpsURLConnection.java:89) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java) at de.schildbach.wallet.util.HttpGetThread.run(HttpGetThread.java:85)
PUT ADDITIONAL COMMENTS TO THE TOP. DOWN HERE NOBODY WILL NOTICE.